This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/49941] [4.7 Regression] segmentation fault in redirect_jump_2
- From: "amodra at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 3 Aug 2011 01:31:43 +0000
- Subject: [Bug rtl-optimization/49941] [4.7 Regression] segmentation fault in redirect_jump_2
- Auto-submitted: auto-generated
- References: <bug-49941-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49941
--- Comment #5 from Alan Modra <amodra at gmail dot com> 2011-08-03 01:29:54 UTC ---
Bernd, that looks very similar to the patch I started to write. Then I saw the
comment in mark_jump_label_1
/* Do not change a previous setting of JUMP_LABEL. If the
JUMP_LABEL slot is occupied by a different label,
create a note for this label. */
So I'm a little concerned that plugging in ret_rtx like that is safe. Hmm, I
suppose it is if you know for sure that any jump that returns doesn't reference
other labels. Is that the case?
I have a patch that handles the JUMP_LABEL replacement in rs6000.md