Wilco Dijkstra writes:
> Hi Richard&Kyrill,
>
>>> I’m in favour of this.
>>
>> Yeah, seems ok to me too. I suppose we ought to update the documentation
>> too:
>
> I've added a note to the documentation. However it is impossible to be
> complete here
> since many targets switch off early schedu
On Tue, Mar 4, 2025 at 9:49 AM Richard Sandiford
wrote:
>
> Wilco Dijkstra writes:
> > Hi Richard&Kyrill,
> >
> >>> I’m in favour of this.
> >>
> >> Yeah, seems ok to me too. I suppose we ought to update the documentation
> >> too:
> >
> > I've added a note to the documentation. However it is i
Hi Richard&Kyrill,
>> I’m in favour of this.
>
> Yeah, seems ok to me too. I suppose we ought to update the documentation too:
I've added a note to the documentation. However it is impossible to be complete
here
since many targets switch off early scheduling under various circumstances. So
I'v
Kyrylo Tkachov writes:
>> On 3 Mar 2025, at 19:58, Wilco Dijkstra wrote:
>>
>>
>> Enable the early scheduler on AArch64 for O3/Ofast. This means GCC15
>> benefits
>> from much faster build times with -O2, but avoids the regressions in lbm
>> which
>> is very sensitive to minor scheduling cha
> On 3 Mar 2025, at 19:58, Wilco Dijkstra wrote:
>
>
> Enable the early scheduler on AArch64 for O3/Ofast. This means GCC15 benefits
> from much faster build times with -O2, but avoids the regressions in lbm which
> is very sensitive to minor scheduling changes due to long FMA chains. We can
Enable the early scheduler on AArch64 for O3/Ofast. This means GCC15 benefits
from much faster build times with -O2, but avoids the regressions in lbm which
is very sensitive to minor scheduling changes due to long FMA chains. We can
then revisit this for GCC16.
gcc:
PR target/118351
