RE: [EXTERNAL] Re: State of AutoFDO in GCC

Hi Xionghu, Yes, I'm pretty sure both of the fixes you mentioned are applicable to GCC 10. I'm not sure what the bar is for backporting fixes. Jan, can you comment on that? The fixes that Xionghu mentioned are: Fix indirect call inlining with AutoFDO https://gcc.gnu.org/git/?p=g

RE: [EXTERNAL] Re: State of AutoFDO in GCC

Hi Jan, Thank you for your reply. I did have you on the TO line in my latest patch: https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596065.html That's the patch I need a review on. I'm looking forward to co-maintaining AutoFDO with you. Thanks, Eugene -Original Message- From: Jan

RE: [EXTERNAL] Re: State of AutoFDO in GCC

Hi David, Thank you for your offer to take on the responsibility of maintaining the AutoFDO-specific portions of the code. I'll be happy to do that with Jan's and other GGC maintainers' help. I hope more people will start using and contributing to AutoFDO. Thanks, Eugene -Original Message

Re: [RFC] Analysis of PR105586 and possible approaches to fix issue

Hi Richard, On 27/07/22 12:28 pm, Richard Biener wrote: > On Tue, Jul 26, 2022 at 8:55 PM Surya Kumari Jangala via Gcc > wrote: >> To fix the issue of insns being assigned different cycles, there are two >> possible solutions: >> >> 1. Modify no_real_insns_p() to treat a DEBUG insn as a non-rea

[RISCV] RISC-V GNU Toolchain Meeting Cancell (July, 28, 2022)

Hi all, Tomorrow meeting will cancel since there are few new topics to discuss. The next meeting will be two weeks later, and we are collecting the themes. If you have any questions want to discuss please mail me and I will add it into the agenda for next meeting.

GCC 12.1.1 Status Report (2022-07-27)

Status == The gcc-12 branch is open for regression and documentation fixes. It is time for a GCC 12.2 release, we are comparatively late with it already. The plan is to create a GCC 12.2 release candidate on August 12th which should give plenty of time to backport or implement important re

Re: State of AutoFDO in GCC

> On Tue, Jul 26, 2022 at 4:13 PM Eugene Rozenfeld via Gcc > wrote: > > > > Hello GCC community. > > > > I started this thread on the state of AutoFDO in GCC more than a year ago. > > Here is the first message in the thread: > > https://gcc.gnu.org/pipermail/gcc/2021-April/235860.html > > > > Si

Re: [RFC] Analysis of PR105586 and possible approaches to fix issue

On Tue, Jul 26, 2022 at 8:55 PM Surya Kumari Jangala via Gcc wrote: > > Hi, > I am working on PR105586. This is a -fcompare-debug failure, with the > differences starting during sched1 pass. The sequence of two instructions in > a basic block (block 4) is flipped with -g. > In addition to this,