> On 12 Nov 2024, at 18:55, Richard Sandiford wrote:
>
> Wilco Dijkstra writes:
>> Hi,
>>
> What do you think about disabling late scheduling as well?
I think this would definitely need separate consideration and evaluation
given the above.
Another thing to con
Wilco Dijkstra writes:
> Hi,
>
What do you think about disabling late scheduling as well?
>>>
>>> I think this would definitely need separate consideration and evaluation
>>> given the above.
>>>
>>> Another thing to consider is the macro fusion machinery. IIRC it works
>>> during schedulin
Hi,
>>> What do you think about disabling late scheduling as well?
>>
>> I think this would definitely need separate consideration and evaluation
>> given the above.
>>
>> Another thing to consider is the macro fusion machinery. IIRC it works
>> during scheduling so if we don’t run any schedulin
Hi Kyrill,
> I think the approach that I’d like to try is using the TARGET_SCHED_DISPATCH
> hooks like x86 does for bdver1-4.
> That would try to exploit the dispatch constraints information in the SWOGs
> rather than the instruction latency and throughput tables.
> That would still require some
On Thu, Oct 31, 2024 at 11:03 AM Wilco Dijkstra wrote:
>
> Hi Andrew,
>
> > I suspect the following scheduling models could be removed due either
> > to hw never going to production or no longer being used by anyone:
> > thunderx3t110.md
> > falkor.md
> > saphira.md
>
> If you're planning to remov
Hi Andrew,
> I suspect the following scheduling models could be removed due either
> to hw never going to production or no longer being used by anyone:
> thunderx3t110.md
> falkor.md
> saphira.md
If you're planning to remove these, it would also be good to remove the
falkor-tag-collision-avoidanc
On Thu, Oct 31, 2024 at 10:25 AM Kyrylo Tkachov wrote:
>
>
>
> > On 31 Oct 2024, at 18:06, Richard Sandiford
> > wrote:
> >
> > Wilco Dijkstra writes:
> >> The early scheduler takes up ~33% of the total build time, however it
> >> doesn't
> >> provide a meaningful performance gain. This is pa
On Thu, Oct 31, 2024 at 10:07 AM Richard Sandiford
wrote:
>
> Wilco Dijkstra writes:
> > The early scheduler takes up ~33% of the total build time, however it
> > doesn't
> > provide a meaningful performance gain. This is partly because modern OoO
> > cores
> > need far less scheduling, partly
> On 31 Oct 2024, at 18:06, Richard Sandiford wrote:
>
> Wilco Dijkstra writes:
>> The early scheduler takes up ~33% of the total build time, however it doesn't
>> provide a meaningful performance gain. This is partly because modern OoO
>> cores
>> need far less scheduling, partly because th
Wilco Dijkstra writes:
> The early scheduler takes up ~33% of the total build time, however it doesn't
> provide a meaningful performance gain. This is partly because modern OoO
> cores
> need far less scheduling, partly because the scheduler tends to create many
> unnecessary spills by increasi
The early scheduler takes up ~33% of the total build time, however it doesn't
provide a meaningful performance gain. This is partly because modern OoO cores
need far less scheduling, partly because the scheduler tends to create many
unnecessary spills by increasing register pressure. Building ap
11 matches
Mail list logo
