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
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 loop, as I
interpret two separate experiments.
Am I misinterpreting somet
On Apr 20, 2021, at 9:11 AM, Gabriel Paubert
mailto:paub...@iram.es>> wrote:
(lldb) di -s 0x000103d6 -c 10
libgambit.dylib`___SCMOBJ_to_NONNULLSTRING:
0x103d6 <+1504>: jl 0x103d60026 ; <+1542> at
c_intf.c:3282:9
0x103d60002 <+1506>: orb%al, 0x31(%rbp)
0
I’m seeing an “Illegal Instruction” fault and don’t quite know how to generate
a proper bug report yet.
This is the compiler:
[Bradleys-Mac-mini:~] lucier% /usr/local/gcc-10.3.0/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/usr/local/gcc-10.3.0/bin/gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-10.3.0/l
