public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/49891] [4.7 regression] ICE in redirect_jump_1 Date: Thu, 28 Jul 2011 22:47:00 -0000 [thread overview] Message-ID: <bug-49891-4-5L2zUOXtNg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49891-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49891 --- Comment #1 from Bernd Schmidt <bernds at gcc dot gnu.org> 2011-07-28 22:47:26 UTC --- Author: bernds Date: Thu Jul 28 22:47:21 2011 New Revision: 176905 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176905 Log: PR rtl-optimization/49891 * cfgrtl.c (force_nonfallthru_and_redirect): Set JUMP_LABEL for newly created returnjumps. Modified: trunk/gcc/ChangeLog trunk/gcc/cfgrtl.c
next prev parent reply other threads:[~2011-07-28 22:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-28 22:25 [Bug rtl-optimization/49891] New: " rearnsha at gcc dot gnu.org 2011-07-28 22:47 ` bernds at gcc dot gnu.org [this message] 2011-07-29 10:10 ` [Bug rtl-optimization/49891] " rguenth at gcc dot gnu.org 2012-07-05 16:45 ` ramana at gcc dot gnu.org 2012-07-05 16:57 ` ramana at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-49891-4-5L2zUOXtNg@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).