public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zdenek Dvorak <rakdver@kam.mff.cuni.cz>
To: Ira Rosen <IRAR@il.ibm.com>
Cc: dberlin@dberlin.org, Diego Novillo <dnovillo@google.com>,
		Dorit Nuzman <DORIT@il.ibm.com>,
	dvorakz@suse.cz, gcc-patches@gnu.org
Subject: Re: [patch] Remove redundant calls to copy_virtual_operands
Date: Sun, 12 Aug 2007 19:40:00 -0000	[thread overview]
Message-ID: <20070812194037.GA22763@kam.mff.cuni.cz> (raw)
In-Reply-To: <OF6667480D.99240450-ONC2257331.003A1EA2-C2257331.003CB6C2@il.ibm.com>

Hello,

> > on the other hand, the fact that there are ICEs shows that there is some
> > problem in setting the alias information for the new statements in
> > vectorizer -- if this were correct, the virtual operands would be
> > exactly the same as the ones of the original statement; so although I
> > agree that leaving things to update_ssa is easier to maintain (although
> > possibly much slower), it would be nice if someone could check what does
> > the alias information updating code in vectorizer get wrong,
> 
> Currently the vectorizer both sets a memory tag and copies virtual
> operands. Sometimes, like in the example below, the tag provided by the
> vectorizer is more accurate than the alias information we had before, i.e.,
> the virtual operands of the scalar memory operations (although I only have
> a testcase for this on 4.1.1).

OK, the patch is correct, then.

Zdenek

  reply	other threads:[~2007-08-12 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 12:10 Ira Rosen
2007-08-07 13:06 ` Dorit Nuzman
2007-08-07 13:23   ` Diego Novillo
2007-08-08  8:02     ` Ira Rosen
2007-08-08 12:06       ` Diego Novillo
2007-08-08  9:41     ` Zdenek Dvorak
2007-08-08 11:04       ` Ira Rosen
2007-08-12 19:40         ` Zdenek Dvorak [this message]
2007-08-07 13:22 ` Diego Novillo

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=20070812194037.GA22763@kam.mff.cuni.cz \
    --to=rakdver@kam.mff.cuni.cz \
    --cc=DORIT@il.ibm.com \
    --cc=IRAR@il.ibm.com \
    --cc=dberlin@dberlin.org \
    --cc=dnovillo@google.com \
    --cc=dvorakz@suse.cz \
    --cc=gcc-patches@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).