This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/51471] [4.7 Regression] gcc.c-torture/execute/20040811-1.c and gcc.c-torture/execute/vla-dealloc-1.c fails at -O3 -g on mips64-linux-gnu
- From: "mikpe at it dot uu.se" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Dec 2011 13:10:33 +0000
- Subject: [Bug debug/51471] [4.7 Regression] gcc.c-torture/execute/20040811-1.c and gcc.c-torture/execute/vla-dealloc-1.c fails at -O3 -g on mips64-linux-gnu
- Auto-submitted: auto-generated
- References: <bug-51471-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51471
--- Comment #6 from Mikael Pettersson <mikpe at it dot uu.se> 2011-12-12 13:10:33 UTC ---
(In reply to comment #5)
> So my question is: what is the mechanism that should prevent epilogue insns
> from being moved to before the epilogue?
A full compiler barrier? See PR38644 for an epilogue scheduling bug on ARM
Thumb-1 that got fixed by prefixing the epilogue with a barrier. That PR also
refers to an older PowerPC bug that was fixed in a similar way.