[Bug target/84521] [8 Regression] aarch64: Frame-pointer corruption with setjmp/longjmp and -fomit-frame-pointer
jgreenhalgh at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Thu Feb 22 18:53:00 GMT 2018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521
James Greenhalgh <jgreenhalgh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-02-22
CC| |ramana.radhakrishnan at arm dot co
| |m
Ever confirmed|0 |1
--- Comment #2 from James Greenhalgh <jgreenhalgh at gcc dot gnu.org> ---
It is a bug that we have changed to -fomit-frame-pointer by default for
AArch64. That changes a long standing ABI decision made at the dawn of the
port, and promised as a feature of the architecture. I would like to see this
fixed for GCC 8.
Ramana was testing a patch to fix this and change us back to
-fno-omit-frame-pointer, it (or someone else's patch achieving the same) would
be appreciated as the immediate fix for this issue.
I haven't validated the longer-term problem you mention with
-fomit-frame-pointer.
Ramana, can you pick this up and set us back to the appropriate default?
Otherwise, I can spin a patch. We should fix this urgently, or we miss the good
value that comes from whole-distribution testing.
More information about the Gcc-bugs
mailing list