On Sun, May 24, 2026 at 10:58 PM Paulo Fernando Barbosa Duarte <[email protected]> wrote: > the the actual root cause was that my cross-compiling gcc had the > flag -fno-omit-frame-pointer ON, this was what tripped the bug. > with the flag OFF the bug doesn’t trigger.
How does that work? Even if you don't use x29 as a frame pointer (which you normally do on AArch64, so I doubt that my GCC had that off), surely you still save/restore at least x30? Maybe that could still happen if zero_out_bss got inlined into c_boot_entry, and so did not have its x30 saved? Sergey
