public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luto at mit dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53582] New: [4.6 regression, fixed in 4.7, I think] ICE on valid code Date: Tue, 05 Jun 2012 17:33:00 -0000 [thread overview] Message-ID: <bug-53582-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53582 Bug #: 53582 Summary: [4.6 regression, fixed in 4.7, I think] ICE on valid code Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: luto@mit.edu g++ -O2 segfaults on this code. Tested on gcc (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2). 4.7 and trunk work. 4.5 seems okay as well. struct A { A(); }; unsigned f1(); void f2() { while(true) { unsigned x; try { f1(); } catch(char) { x = (unsigned)-1; } if (x != 1) { new A; continue; } } }
next reply other threads:[~2012-06-05 17:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-05 17:33 luto at mit dot edu [this message] 2012-06-06 9:19 ` [Bug c++/53582] [4.6 regression] " rguenth 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-53582-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).