------- Comment #7 from hp at gcc dot gnu dot org 2009-01-26 12:46 -------
(In reply to comment #6)
> Sounds like this could maybe be a dup of bug 38952, where the frame pointer
> is incorrectly calculated when setjmp saves it in the jmp_buf, and therefore
> restored to an incorrect value by longjmp. For a quick test without
> rebuilding
> your compiler, see if "-mpreferred-stack-boundary=2" or "-mno-stackrealign"
> fixes the failure in built-in-setjmp.c; if so there's a patch in the PR that
> should help.
I don't have those options :) and the stack-alignment options I have make no
difference - but I think you might on the right track. I'll investigate
whether
this is just a sign of CRIS suffering from lack of
TARGET_BUILTIN_SETJMP_FRAME_VALUE.
Can't be a dup though, same target bug but different targets.
Fixing one won't fix the other. :) Right, changing component to target.
Thanks!
--
hp at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |hp at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Component|middle-end |target
Last reconfirmed|2008-12-23 22:17:16 |2009-01-26 12:46:38
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38609
