> On 30 Apr 2024, at 08:33, Iain Sandoe wrote:
>
> Hi,
>
>> On 30 Apr 2024, at 00:39, Andrew Pinski via Gcc wrote:
>>
>> On Mon, Apr 29, 2024 at 4:26 PM Lucier, Bradley J via Gcc
>> wrote:
>>>
>>> The question: How to interpret scheduling info with the compiler listed
>>> below.
>>>
>>>
Hi,
> On 30 Apr 2024, at 00:39, Andrew Pinski via Gcc wrote:
>
> On Mon, Apr 29, 2024 at 4:26 PM Lucier, Bradley J via Gcc
> wrote:
>>
>> The question: How to interpret scheduling info with the compiler listed
>> below.
>>
>> Specifically, a tight loop that was reported to be scheduled in 23
On Mon, Apr 29, 2024 at 4:26 PM Lucier, Bradley J via Gcc
wrote:
>
> The question: How to interpret scheduling info with the compiler listed below.
>
> Specifically, a tight loop that was reported to be scheduled in 23 cycles (as
> I understand it) actually executes in a little over 2 cycles per
That should be 4 cycles per loop, sorry.
> On Apr 29, 2024, at 7:24 PM, Lucier, Bradley J wrote:
>
> Specifically, a tight loop that was reported to be scheduled in 23 cycles (as
> I understand it) actually executes in a little over 2 cycles per loop
