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 middle-end/51761] New: [4.7 Regression] ICE in verify_gimple_stmt, at tree-cfg.c:4241
Date: Thu, 05 Jan 2012 10:59:00 -0000 [thread overview]
Message-ID: <bug-51761-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51761
Bug #: 51761
Summary: [4.7 Regression] ICE in verify_gimple_stmt, at
tree-cfg.c:4241
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: rguenth@gcc.gnu.org
CC: matz@gcc.gnu.org
Target: i?86-*-*
Created attachment 26247
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26247
preprocessed source
Building strongswan reveals:
> ./cc1 -quiet chunk.i -O -m32
chunk.c: In function 'chunk_printable':
chunk.c:558:7: internal compiler error: in verify_gimple_stmt, at
tree-cfg.c:4314
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
#1 0x0000000000b57d26 in verify_gimple_stmt (stmt=0x7ffff58bbf28)
at /space/rguenther/src/svn/trunk/gcc/tree-cfg.c:4314
4314 gcc_unreachable ();
(gdb) call debug_gimple_stmt (stmt)
<<< Unknown GIMPLE statement: gimple_with_cleanup_expr >>>
next reply other threads:[~2012-01-05 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 10:59 rguenth at gcc dot gnu.org [this message]
2012-01-05 11:00 ` [Bug middle-end/51761] " rguenth at gcc dot gnu.org
2012-01-05 11:09 ` jakub at gcc dot gnu.org
2012-01-05 11:22 ` jakub at gcc dot gnu.org
2012-01-05 12:02 ` jakub at gcc dot gnu.org
2012-01-05 14:04 ` jason at redhat dot com
2012-01-05 15:10 ` jakub at gcc dot gnu.org
2012-01-05 15:21 ` 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-51761-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: link
Be 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).