public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/51590] New: [4.7 Regression] ICE in gsi_for_stmt, at gimple-iterator.c:560 Date: Fri, 16 Dec 2011 21:47:00 -0000 [thread overview] Message-ID: <bug-51590-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51590 Bug #: 51590 Summary: [4.7 Regression] ICE in gsi_for_stmt, at gimple-iterator.c:560 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org Host: x86_64-unknown-linux-gnu With 4.7.0 20111216 I get an ICE: $ g++ -c -O3 test-it-25.ii test-it-25.ii: In member function 'void v8::internal::RelocIterator::next()': test-it-25.ii:41:14: internal compiler error: in gsi_for_stmt, at gimple-iterator.c:560 But not with "-m32", "-O2" nor with GCC 4.6.2. The failing assert is: /* Finds iterator for STMT. */ gimple_stmt_iterator gsi_for_stmt (gimple stmt) { ... gcc_unreachable (); }
next reply other threads:[~2011-12-16 21:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-16 21:47 burnus at gcc dot gnu.org [this message] 2011-12-16 22:09 ` [Bug middle-end/51590] " burnus at gcc dot gnu.org 2011-12-18 13:00 ` burnus at gcc dot gnu.org 2011-12-18 13:14 ` dimhen at gmail dot com 2011-12-19 9:25 ` jakub at gcc dot gnu.org 2011-12-19 9:28 ` jakub at gcc dot gnu.org 2011-12-19 11:18 ` jakub at gcc dot gnu.org 2011-12-19 14:26 ` jakub at gcc dot gnu.org 2011-12-19 14:30 ` jakub 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-51590-4@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).