public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/41906]  New: [4.5 Regression] ICE with catch(...) and -fpermissive
Date: Mon, 02 Nov 2009 13:41:00 -0000	[thread overview]
Message-ID: <bug-41906-1771@http.gcc.gnu.org/bugzilla/> (raw)

The following valid code snippet triggers an ICE on trunk when compiled with
"-fpermissive":

===================
void foo();

void bar()
{
  try { foo(); }
  catch (...) {}
  catch (int) {}
}
===================

bug.cc: In function 'void bar()':
bug.cc:6:3: warning: '...' handler must be the last handler for its try block
bug.cc:3:6: internal compiler error: Segmentation fault
Please submit a full bug report, [etc.]

The bug appeared between 2009-09-01 and 2009-09-17.


-- 
           Summary: [4.5 Regression] ICE with catch(...) and -fpermissive
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, monitored
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: reichelt at gcc dot gnu dot org


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


             reply	other threads:[~2009-11-02 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 13:41 reichelt at gcc dot gnu dot org [this message]
2009-11-02 13:41 ` [Bug c++/41906] " reichelt at gcc dot gnu dot org
2009-11-05 15:58 ` jason at gcc dot gnu dot org
2009-11-05 16:03 ` jason at gcc dot gnu dot org
2009-11-09 13:05 ` rguenth at gcc dot gnu dot org
2009-11-26 16:51 ` matz at gcc dot gnu dot org
2009-11-27 13:09 ` matz at gcc dot gnu dot org
2009-11-27 13:26 ` matz at gcc dot gnu dot org
2009-12-11 23:41 ` hjl at gcc dot gnu dot 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-41906-1771@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).