This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/38609] [4.4 Regression]: gcc.c-torture/execute/built-in-setjmp.c execute -O2 and above
- From: "hp at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Mar 2009 05:35:43 -0000
- Subject: [Bug target/38609] [4.4 Regression]: gcc.c-torture/execute/built-in-setjmp.c execute -O2 and above
- References: <bug-38609-507@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #9 from hp at gcc dot gnu dot org 2009-03-17 05:35 -------
(In reply to comment #8)
> Guess it probably won't be TARGET_BUILTIN_SETJMP_FRAME_VALUE then.
At any rate, changing it to hard_frame_pointer_rtx doesn't help by itself.
(Resulting diffs in RTL dumps are gone after 132r.unshare, for r144898.)
Either, GCC should punt and force p to the stack, or calculate p / keep track
of the stack-pointer correctly: the value is off by 20 when used after the
longjump. (It should be "move.d [$sp+28],$r10", not $sp+8.) Right, that's the
"sp -= 20" due to the __builtin_alloca (20) before the __builtin_setjmp call.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38609