public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/23626] New: [4.1 Regression] ICE after cunrolling Date: Mon, 29 Aug 2005 17:41:00 -0000 [thread overview] Message-ID: <20050829174053.23626.pinskia@gcc.gnu.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1129 bytes --] The following C++ code currently fails at -O2 -fnon-call-exceptions: extern "C" void abort (); int a[3]; int f () { int sum = 0; try { for (int i = 0; i < 3; ++i) sum += a[i]; } catch (...) { abort (); } return sum; } I think someone forgets to cleanup the eh regions after unrolling: t.cc: In function int f(): t.cc:2: error: BB 0 last statement has incorrectly set region t.cc:2: internal compiler error: verify_flow_info failed Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -- Summary: [4.1 Regression] ICE after cunrolling Product: gcc Version: 4.1.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,rakdver at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23626
next reply other threads:[~2005-08-29 17:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-29 17:41 pinskia at gcc dot gnu dot org [this message] 2005-08-29 17:41 ` [Bug tree-optimization/23626] " pinskia at gcc dot gnu dot org 2005-08-29 17:49 ` pinskia at gcc dot gnu dot org 2005-08-30 13:34 ` rakdver at gcc dot gnu dot org 2005-08-31 10:16 ` rakdver at gcc dot gnu dot org 2005-09-02 9:05 ` cvs-commit at gcc dot gnu dot org 2005-09-02 9:12 ` rakdver 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=20050829174053.23626.pinskia@gcc.gnu.org \ --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).