public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63593] ICE: verify_gimple failed: incompatible types in PHI argument 0 with -O3 -fno-tree-vectorize
Date: Mon, 16 Feb 2015 12:08:00 -0000	[thread overview]
Message-ID: <bug-63593-4-xX0ed1sRwg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63593-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63593

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Ok, one issue is that predictive commoning removes statements and releases
SSA names while they are still in use, and then allocates new SSA names before
eventually releasing the using stmts.

Delaying that keeps released SSA names in the IL (better than filled with
invalid re-used ones) after the transform callback.  Now we enter
gimple_duplicate_loop_to_header_edge with that "invalid" IL...

But at least it fixes this testcase and the related one.


  parent reply	other threads:[~2015-02-16 12:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-19  8:22 [Bug tree-optimization/63593] New: " zsojka at seznam dot cz
2014-11-24 19:04 ` [Bug tree-optimization/63593] " mpolacek at gcc dot gnu.org
2014-11-24 19:25 ` mpolacek at gcc dot gnu.org
2014-11-25 19:02 ` mpolacek at gcc dot gnu.org
2014-12-19 13:41 ` jakub at gcc dot gnu.org
2015-02-16 10:59 ` rguenth at gcc dot gnu.org
2015-02-16 12:08 ` rguenth at gcc dot gnu.org [this message]
2015-02-16 14:52 ` rguenth at gcc dot gnu.org
2015-02-16 14:52 ` rguenth at gcc dot gnu.org
2015-02-20  7:32 ` rguenth at gcc dot gnu.org
2015-02-23 10:18 ` rguenth at gcc dot gnu.org
2015-02-25 10:41 ` rguenth at gcc dot gnu.org
2015-02-25 11:17 ` 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-63593-4-xX0ed1sRwg@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).