public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Ira Rosen <IRAR@il.ibm.com>
Cc: gcc-patches@gnu.org
Subject: Re: [patch] Remove redundant calls to copy_virtual_operands
Date: Tue, 07 Aug 2007 13:22:00 -0000	[thread overview]
Message-ID: <46B871CB.1050400@google.com> (raw)
In-Reply-To: <OF930B00A8.8262D5E2-ONC2257330.0032AB21-C2257330.0042B670@il.ibm.com>

On 8/7/07 8:08 AM, Ira Rosen wrote:

>       * tree-vect-transform.c (vectorizable_store): Remove call to
>       copy_virtual_operands() and call mark_symbols_for_renaming() for
>       the created vector store.
>       (vect_setup_realignment): Don't call copy_virtual_operands() and
>       update_vuses_to_preheader().
>       (vectorizable_load): Don't call copy_virtual_operands().
>       (update_vuses_to_preheader): Remove.

Well, it's certainly safe to do this.  However, you may be marking more
symbols for renaming than strictly necessary.  Have you compared compile
times?  If you are marking more symbols for renaming than before, you
are probably increasing the time needed to update the SSA form.

It may certainly make it easier to maintain, but if the compile times
are a problem, I would suggest going with what you had before.  Though
I'd be willing to bet that this won't really affect compile times all
that much.

      parent reply	other threads:[~2007-08-07 13:22 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
2007-08-07 13:22 ` Diego Novillo [this message]

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=46B871CB.1050400@google.com \
    --to=dnovillo@google.com \
    --cc=IRAR@il.ibm.com \
    --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).