On 9/11/18 7:38 AM, Vlad Lazar wrote:
> Hi.
>
> This patch makes the scheduler prefer instructions with higher cost if
> two given instructions are equally good.
> Issuing more restricted instructions first is particularly useful on
> in-order cores because it increases the
> number of dual issue
On 9/11/18 9:00 AM, Kyrill Tkachov wrote:
> Hi Ramana,
>
> On 11/09/18 15:55, Ramana Radhakrishnan wrote:
>> On Tue, 11 Sep 2018, 14:38 Vlad Lazar, wrote:
>>
>> > Hi.
>> >
>> > This patch makes the scheduler prefer instructions with higher cost
>> if two
>> > given instructions are equally good.
>
> > This to me feels like the wrong approach as it feels like you are assuming
> > INSN_COST is latency in some way ? Surely, we shouldn't be introducing
> > INSN_COST based stuff into the scheduler.
> >
> > Have you investigated using TARGET_SCHED_ADJUST_COST (IIRC, look for the
> > right name
Hi Ramana,
On 11/09/18 15:55, Ramana Radhakrishnan wrote:
On Tue, 11 Sep 2018, 14:38 Vlad Lazar, wrote:
> Hi.
>
> This patch makes the scheduler prefer instructions with higher cost if two
> given instructions are equally good.
> Issuing more restricted instructions first is particularly usefu
On Tue, 11 Sep 2018, 14:38 Vlad Lazar, wrote:
> Hi.
>
> This patch makes the scheduler prefer instructions with higher cost if two
> given instructions are equally good.
> Issuing more restricted instructions first is particularly useful on
> in-order cores because it increases the
> number of du
Hi.
This patch makes the scheduler prefer instructions with higher cost if two
given instructions are equally good.
Issuing more restricted instructions first is particularly useful on in-order
cores because it increases the
number of dual issue opportunities.
For example, on AArch64, instead
