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/47632] New: [4.6 Regression] ICE: verify_flow_info failed: BB 4 can not throw but has an EH edge with -fnon-call-exceptions -ftrapv and operator new[]
Date: Mon, 07 Feb 2011 13:08:00 -0000	[thread overview]
Message-ID: <bug-47632-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47632

           Summary: [4.6 Regression] ICE: verify_flow_info failed: BB 4
                    can not throw but has an EH edge with
                    -fnon-call-exceptions -ftrapv and operator new[]
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


Created attachment 23264
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23264
reduced testcase

Compiler output:
$ gcc -O -fnon-call-exceptions -ftrapv testcase.C 
testcase.C: In function 'void foo(S<char>*)':
testcase.C:11:1: error: BB 4 can not throw but has an EH edge
testcase.C:11: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:
r169824 - crash
r160000 - OK


             reply	other threads:[~2011-02-07 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 13:08 zsojka at seznam dot cz [this message]
2011-02-07 16:02 ` [Bug tree-optimization/47632] " rguenth at gcc dot gnu.org
2011-02-07 16:27 ` rguenth at gcc dot gnu.org
2011-02-08 10:45 ` rguenth at gcc dot gnu.org
2011-02-08 10:51 ` rguenth at gcc dot gnu.org
2011-02-08 14:48 ` 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-47632-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).