public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/54669] [4.8 regression] verify_flow_info failure after loop unrolling with -fnon-call-exceptions Date: Sat, 22 Sep 2012 19:50:00 -0000 [thread overview] Message-ID: <bug-54669-4-B2hJmQAfUf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54669-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54669 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-09-22 Component|middle-end |tree-optimization Target Milestone|--- |4.8.0 Summary|[4.8 Regression] ICE: |[4.8 regression] |verify_flow_info failed: BB |verify_flow_info failure |5 last statement has |after loop unrolling with |incorrectly set lp with |-fnon-call-exceptions |-fnon-call-exceptions | Ever Confirmed|0 |1 --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-09-22 19:50:11 UTC --- I guess it's the transformation of array accesses with variable index into array accesses with fixed index in conjunction with -fnon-call-exceptions.
next prev parent reply other threads:[~2012-09-22 19:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-22 10:41 [Bug middle-end/54669] New: [4.8 Regression] ICE: verify_flow_info failed: BB 5 last statement has incorrectly set lp " zsojka at seznam dot cz 2012-09-22 13:31 ` [Bug middle-end/54669] " polacek at redhat dot com 2012-09-22 14:24 ` polacek at redhat dot com 2012-09-22 19:50 ` ebotcazou at gcc dot gnu.org [this message] 2012-09-22 19:52 ` [Bug tree-optimization/54669] [4.8 regression] verify_flow_info failure after loop unrolling " ebotcazou at gcc dot gnu.org 2012-09-22 20:04 ` polacek at redhat dot com 2012-09-22 20:35 ` ebotcazou at gcc dot gnu.org 2012-09-23 20:38 ` ebotcazou at gcc dot gnu.org 2012-09-23 20:40 ` ebotcazou 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-54669-4-B2hJmQAfUf@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).