From: Andrew MacLeod <amacleod@redhat.com>
To: Jeff Law <law@redhat.com>
Cc: Diego Novillo <dnovillo@redhat.com>,
Dale Johannesen <dalej@apple.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa vs lno] who is right?
Date: Fri, 26 Mar 2004 18:08:00 -0000 [thread overview]
Message-ID: <1080315577.12834.102.camel@p4> (raw)
In-Reply-To: <200403261530.i2QFUU0n014162@speedy.slc.redhat.com>
On Fri, 2004-03-26 at 10:30, law@redhat.com wrote:
> In message <1080308082.12528.27.camel@p4>, Andrew MacLeod writes:
> >I have some minor changes to copyrename in the queue, but I doubt it
> >will affect this. Since there is a constant in the arguments of the PHI,
> >it must have been renamed due to a copy between a temp and maxmin_Result
> >elsewhere in the program. The hope was that we'd be able to get rid of
> >the copy. Looks like not, unless one or more of the PHIs can be
> >optimized away. :-)
> I'd expect DOM to propagate the constants so that there were no uses
> of maxmin_Result_140, maxmin_Result_142, then I'd expect DCE to zap the
> useless PHIs.
>
> Alternatively Zdenek's block trivial PHI removal code may zap them.
>
> But again, I think step #1 is to figure out how we got them in the first
> place.
> jeff
>
It would be pretty easy, something like:
maxmin_Result_140 = PHI <1(10)>;
T.55_142 = PHI <2(10)>;
<...>
maxmin_Result_133 = T.55_142
could result in the 2 PHI nodes since we'd rename T.55_142 to
maxmin_Result_133 in hopes of getting rid of the copy.
It could also happen if T.55_142 is later used as a PHI argument to a
maxmin_Result PHI result.
Andrew
next prev parent reply other threads:[~2004-03-26 15:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 5:32 Dale Johannesen
2004-03-26 6:34 ` Diego Novillo
2004-03-26 6:35 ` Dale Johannesen
2004-03-26 7:08 ` Diego Novillo
2004-03-26 7:27 ` Andrew Pinski
2004-03-26 16:21 ` Andrew MacLeod
2004-03-26 16:31 ` Diego Novillo
2004-03-26 16:40 ` Andrew MacLeod
2004-03-26 17:48 ` law
2004-03-26 18:08 ` Andrew MacLeod [this message]
2004-03-26 18:10 ` law
2004-03-26 18:49 ` Dale Johannesen
2004-03-26 16:44 ` law
2004-03-26 17:42 ` Diego Novillo
2004-03-26 18:51 ` Zdenek Dvorak
2004-03-26 20:15 ` Dale Johannesen
2004-03-26 21:09 ` Devang Patel
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=1080315577.12834.102.camel@p4 \
--to=amacleod@redhat.com \
--cc=dalej@apple.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=law@redhat.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).