public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/47086] New: ICE: verify_flow_info failed: BB 3 can not throw but has an EH edge with -O -fexceptions -fnon-call-exceptions -ftrapv Date: Tue, 28 Dec 2010 20:48:00 -0000 [thread overview] Message-ID: <bug-47086-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47086 Summary: ICE: verify_flow_info failed: BB 3 can not throw but has an EH edge with -O -fexceptions -fnon-call-exceptions -ftrapv Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz CC: steven@gcc.gnu.org Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 22860 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22860 reduced testcase (from gcc.c-torture/execute/pr43220.c) Compiler output: $ gcc -O -fexceptions -fnon-call-exceptions -ftrapv pr47086.c pr47086.c: In function 'foo': pr47086.c:2:1: error: BB 3 can not throw but has an EH edge pr47086.c:2:1: internal compiler error: verify_flow_info failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r168296 - crash I don't know if this is a regression or not.
next reply other threads:[~2010-12-28 20:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-28 20:48 zsojka at seznam dot cz [this message] 2010-12-29 2:47 ` [Bug tree-optimization/47086] [4.5/4.6 Regression] " hjl.tools at gmail dot com 2011-01-03 21:40 ` rguenth at gcc dot gnu.org 2011-01-10 16:05 ` law at redhat dot com 2011-01-11 14:17 ` law at redhat dot com 2011-01-11 14:17 ` law at gcc dot gnu.org 2011-01-11 14:21 ` law at redhat dot com 2011-01-11 14:26 ` zsojka at seznam dot cz 2011-01-11 14:43 ` law at redhat dot com 2011-01-11 14:51 ` law at redhat dot com
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-47086-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).