This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/61373] neon registers restored incorrectly with -mapcs-frame -O -fno-omit-frame-pointer
- From: "Rolf dot Woehrmann at t-online dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 16 Aug 2017 14:22:48 +0000
- Subject: [Bug target/61373] neon registers restored incorrectly with -mapcs-frame -O -fno-omit-frame-pointer
- Auto-submitted: auto-generated
- References: <bug-61373-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61373
Rolf.Woehrmann@t-online.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Rolf.Woehrmann@t-online.de
--- Comment #4 from Rolf.Woehrmann@t-online.de ---
Hi
this problem of generating wrong restore code for neon registers is still
happening in 7.2.0 when using the -mapcs-frame option.
Since this is just wrong code generation which should never happen, I highly
recommend to either emit a warning when using neon with -mapcs-frame option
(like together with -mfpu=neon-xyz) or simply fix the code generation bug.
I ran into this problem and spent aka wasted the last 3 days to find this out.
A simple warning at least should have avoided this. In most of the cases we
could remove -mapcs-frame if we only knew.
Gret Thanks
Rolf