public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50617] [4.5/4.6/4.7 Regression] ICE: RTL flag check: INSN_ANNULLED_BRANCH_P used with unexpected rtx code 'simplify_immed_subreg' in output_bb, at config/pa/pa.c:6631 Date: Thu, 27 Oct 2011 10:35:00 -0000 [thread overview] Message-ID: <bug-50617-4-O7Cdoi148Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50617-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50617 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 Status|UNCONFIRMED |NEW Last reconfirmed| |2011-10-27 CC| |dnovillo at gcc dot gnu.org Target Milestone|4.7.0 |4.5.4 Summary|[4.5, 4.6, 4.7 Regression] |[4.5/4.6/4.7 Regression] |ICE: RTL flag check: |ICE: RTL flag check: |INSN_ANNULLED_BRANCH_P used |INSN_ANNULLED_BRANCH_P used |with unexpected rtx code |with unexpected rtx code |'simplify_immed_subreg' in |'simplify_immed_subreg' in |output_bb, at |output_bb, at |config/pa/pa.c:6631 |config/pa/pa.c:6631 Ever Confirmed|0 |1 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-10-27 10:34:53 UTC --- Diego, any reason why you didn't prefix those public functions in gimple-streamer.[ch]?
next prev parent reply other threads:[~2011-10-27 10:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-04 19:07 [Bug lto/50617] New: [4.7 " danglin at gcc dot gnu.org 2011-10-05 10:09 ` [Bug lto/50617] " rguenth at gcc dot gnu.org 2011-10-22 16:41 ` [Bug target/50617] [4.5, 4.6, 4.7 " danglin at gcc dot gnu.org 2011-10-27 10:35 ` rguenth at gcc dot gnu.org [this message] 2011-10-27 11:44 ` [Bug target/50617] [4.5/4.6/4.7 " dave.anglin at bell dot net 2011-10-29 18:59 ` danglin at gcc dot gnu.org 2011-10-29 20:23 ` danglin at gcc dot gnu.org 2011-10-29 21:44 ` danglin 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-50617-4-O7Cdoi148Q@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).