public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Joe Buck <jbuck@synopsys.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] copy propagation and the abstraction penalty
Date: Thu, 15 May 2003 22:20:00 -0000	[thread overview]
Message-ID: <20030515221748.GC10321@redhat.com> (raw)
In-Reply-To: <1053007822.4382.137.camel@frodo.toronto.redhat.com>

On Thu, May 15, 2003 at 10:10:22AM -0400, Diego Novillo wrote:
>         I'm also wondering if we could change the
>         may-alias between this and UV2150 to a must-alias, which would
>         completely free this program from aliasing problems:

Indeed.  And for this case I definitely think it's the right thing to do.

IMO constant propagation should be able to take

    T.8_2 = &<UVa150>;
    {
      struct complex * const this;

      this_3 = (struct complex * const)T.8_2;
      {
        this->re = 1.0e+0;

and turn it into

	(&<UVa150>)->re = 1.0e+0

which folds to

	<UVa150>.re = 1.0e+0

At which point we have no aliasing problem, and a subsequent round
of constant propagation ought to be able to send 1.0e+0 to its 
destination.


r~

  parent reply	other threads:[~2003-05-15 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 22:45 Joe Buck
2003-05-15  3:15 ` Andrew Pinski
2003-05-15 14:10 ` Diego Novillo
2003-05-15 17:09   ` Joe Buck
2003-05-15 17:28     ` Joe Buck
2003-05-15 18:01     ` Daniel Berlin
2003-05-15 22:20   ` Richard Henderson [this message]
2003-05-15 22:48     ` Joe Buck
2003-05-15 22:51       ` Joe Buck

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=20030515221748.GC10321@redhat.com \
    --to=rth@redhat.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    /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).