James Greenhalgh wrote:
> This seems like a bit of a theoretical issue as we would normally build
> libgcc with -fno-omit-frame-pointer anyway, but it can't hurt to guarantee
> this, so OK.
It's not theoretical since there were multiple users reporting unwinding issues,
so clearly doing CFLAGS="-fomit-frame-pointer" is popular. While this patch
fixes AArch64, this bug affects all targets. Obviously -fno-omit-frame-pointer
should be an automatic default for the libgcc unwind code until the Dwarf
engine is fixed and it is made clear what the target unwind interface is.
Wilco
