public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26197] [4.2 regression] ICE in is_old_name, at tree-into-ssa.c:466
Date: Fri, 10 Feb 2006 20:24:00 -0000 [thread overview]
Message-ID: <20060210202436.27842.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26197-1771@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from law at redhat dot com 2006-02-10 20:24 -------
This is a bug in the vectorizer and has absolutely nothing to do with PR26169.
The vectorizer is twiddling things such that the set of virtual operands
changes
for the statement in question. ie, if you look at the statement before and
after the vectorizer runs it has the form:
# TMT.32D.2670_172 = V_MAY_DEF <TMT.32D.2670_17>;
D.2524_41->a0D.2385 = D.2477.a0D.2385;
However, if you were to call update_stmt on the statement immediately after
the vectorizer is complete, then dumped the statement again, you'd have:
# TMT.32D.2670_172 = V_MAY_DEF <TMT.32D.2670_17>;
# VUSE <SFT.11D.2649>;
# VUSE <SFT.12D.2650>;
D.2524_41->a0D.2385 = D.2477.a0D.2385;
That's a clear indication that this bug is actually in the vectorizer. Not
VRP or the SSA updating code.
When a pass twiddles aliasing information such that the set of virtual operands
would change on a statement that is a bug if the statement is not properly
updated.
Jeff
--
law at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|law at gcc dot gnu dot org |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26197
next prev parent reply other threads:[~2006-02-10 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 14:51 [Bug tree-optimization/26197] New: " reichelt at gcc dot gnu dot org
2006-02-09 15:10 ` [Bug tree-optimization/26197] " pinskia at gcc dot gnu dot org
2006-02-09 15:45 ` pinskia at gcc dot gnu dot org
2006-02-09 16:03 ` law at redhat dot com
2006-02-10 20:24 ` law at redhat dot com [this message]
2006-02-12 19:24 ` rakdver at gcc dot gnu dot org
2006-02-13 16:23 ` dorit at il dot ibm dot com
2006-02-16 12:52 ` rakdver at gcc dot gnu dot org
2006-02-16 17:54 ` rakdver at gcc dot gnu dot org
2006-02-17 19:54 ` rakdver at gcc dot gnu dot org
2006-02-19 16:10 ` dorit at il dot ibm dot com
2006-02-28 8:43 ` [Bug tree-optimization/26197] [4.2 regression] ICE in is_old_name with vectorizer dorit at il dot ibm dot com
2006-02-28 14:40 ` dnovillo at gcc dot gnu dot org
2006-03-01 12:35 ` dorit at il dot ibm dot com
2006-03-02 4:44 ` pinskia at gcc dot gnu dot org
2006-03-03 18:00 ` pinskia at gcc dot gnu dot org
2006-04-05 18:38 ` pinskia at gcc dot gnu dot org
2006-06-04 17:41 ` mmitchel at gcc dot gnu dot org
2006-07-24 19:50 ` patchapp at dberlin dot org
2006-08-10 12:07 ` dorit at gcc dot gnu dot org
2006-08-11 14:53 ` reichelt at gcc dot gnu dot org
2006-08-29 17:04 ` pinskia 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=20060210202436.27842.qmail@sourceware.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: 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).