Comment by rwmj
10 months ago
That was in 2012. Does it still occur on modern GCC?
There definitely have been regressions with frame pointers being enabled, although we've fixed all the ones we've found in current (2024) Fedora.
10 months ago
That was in 2012. Does it still occur on modern GCC?
There definitely have been regressions with frame pointers being enabled, although we've fixed all the ones we've found in current (2024) Fedora.
I think so and I vaguely seem to recall -fno-schedule-insns2 being the only thing that fixes it. To get the full power of frame pointers and hackable binary, what I use is:
The only flag that's potentially problematic is -fno-optimize-sibling-calls since it breaks the optimal approach to writing interpreters and slows down code that's written in a more mathematical style.
Pretty sure unwinding thumb generated by GCC is still non-unwindable via FPs. That's been a pain.