t;> Subject: Re: [PATCH] scheduler bug fix for AArch64 insn fusing
>> SCHED_GROUP usage
>> To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
>> Cc: Jim Wilson <jim.wil...@linaro.org>
>>
>>
>> ping^2
>>
>> On Fri, Jul 2
On Sun, 2017-09-10 at 19:45 +0200, Jim Wilson wrote:
> -- Forwarded message --
> From: Jim Wilson <jim.wil...@linaro.org>
> Date: Tue, Sep 5, 2017 at 8:04 PM
> Subject: Re: [PATCH] scheduler bug fix for AArch64 insn fusing
> SCHED_GROUP usage
> To: "
ping^2
On Fri, Jul 21, 2017 at 3:09 PM, Jim Wilson wrote:
> Ping.
>
> https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00779.html
>
> On Thu, Jul 13, 2017 at 3:00 PM, Jim Wilson wrote:
>> The AArch64 port uses SCHED_GROUP to mark instructions that get
Ping.
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00779.html
On Thu, Jul 13, 2017 at 3:00 PM, Jim Wilson wrote:
> The AArch64 port uses SCHED_GROUP to mark instructions that get fused
> at issue time, to ensure that they will be issued together. However,
> in the
The AArch64 port uses SCHED_GROUP to mark instructions that get fused
at issue time, to ensure that they will be issued together. However,
in the scheduler, use of a SCHED_GROUP forces all other instructions
to issue in the next cycle. This is wrong for AArch64 ports using
insn fusing which can