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="-
: 31 July 2017 16:57
> To: GCC Patches; James Greenhalgh
> Cc: nd
> Subject: [PATCH][AArch64] PR71951: Fix unwinding with -fomit-frame-pointer
>
> As described in PR71951, if libgcc is built with -fomit-frame-pointer,
> unwinding crashes, for example while doing a backtrace. T
ping
From: Wilco Dijkstra
Sent: 31 July 2017 16:57
To: GCC Patches; James Greenhalgh
Cc: nd
Subject: [PATCH][AArch64] PR71951: Fix unwinding with -fomit-frame-pointer
As described in PR71951, if libgcc is built with -fomit-frame-pointer,
unwinding crashes, for example while doing a
As described in PR71951, if libgcc is built with -fomit-frame-pointer,
unwinding crashes, for example while doing a backtrace. The underlying
reason is the Dwarf unwinder does not setup the frame pointer register
in the initialization code. When later unwinding a function that uses
the frame poin
