public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew MacLeod <amacleod@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Jeff Law <law@redhat.com>, Richard Henderson <rth@redhat.com>,
gcc-bugs <gcc-bugs@gcc.gnu.org>
Subject: Re: Bug 14562 : copyrename & PRE
Date: Mon, 15 Mar 2004 18:17:00 -0000 [thread overview]
Message-ID: <1079374594.4007.3593.camel@p4> (raw)
In-Reply-To: <Pine.LNX.4.56.0403151221120.11905@dberlin.org>
On Mon, 2004-03-15 at 12:58, Daniel Berlin wrote:
> > >
> > > It probably wouldn't take long for you to see what wrong. Either its
> > > something I did about PARM_DECLs, or an assumption PRE is making, Im not
> > > sure which.
> >
> > I'll check it out
> >
>
> It looks like we have two occurrences of the expression with copyrename,
> and one without it.
>
> EUSE (k_29 * 4) [class:1 phiop:0 bb:1 ]
> EUSE (k_29 * 4) [class:2 phiop:0 bb:1 ]
> EUSE () [class:-1 phiop:1 bb:6 ]
> EUSE () [class:-1 phiop:1 bb:5 ]
>
> without copyrename:
>
> EUSE (T.1_29 * 4) [class:2 phiop:0 bb:1 ]
> EUSE () [class:-1 phiop:1 bb:4 ]
> EUSE () [class:-1 phiop:1 bb:3 ]
>
>
> PRE is not value based (right now, i'm working on a GVN-PRE algorithm), so
> this is why it picks it up when you have k, but not T (because in one case
> you have one k * 4 expression, and one t * 4 expression, and in the other
> case you have two k * 4 expressions)
>
> The results of PRE look fine given the code in both cases (in one case,
> the expression we are looking at is modified in between the phi and the
> use, and in the other case, it isn't, because we are picking up the extra
> expression, and that's the one getting optimized).
>
> Do you see something actually wrong with the code PRE is producing?
>
No, I was wondering why it triggers. There shouldn't be any more uses of
k_29 than there were of T.1_29. copyrename simply replaces T.1_29 with
k_29. Why do you get two occurrences after the transformation?
whats the 'class' thing? There seems to be a class 1 use of k_29 that
doesnt exist when its T.1_29.
-fno-tree-pre makes it work, for what thats worth, so I figured it might
have something to do with the extra stuff PRE is doing...
Andrew
next prev parent reply other threads:[~2004-03-15 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 15:36 Andrew MacLeod
[not found] ` <B1E9BD74-769B-11D8-BAA6-000A95DA505C@dberlin.org>
2004-03-15 16:17 ` Daniel Berlin
2004-03-15 16:42 ` Andrew MacLeod
2004-03-15 16:50 ` Daniel Berlin
2004-03-15 17:58 ` Daniel Berlin
2004-03-15 18:17 ` Andrew MacLeod [this message]
2004-03-15 18:27 ` Daniel Berlin
2004-03-15 18:31 ` Andrew MacLeod
2004-03-15 18:52 ` Daniel Berlin
2004-03-15 19:50 ` Andrew MacLeod
2004-03-15 19:59 ` Daniel Berlin
2004-03-15 20:20 ` Andrew MacLeod
2004-03-15 20:45 ` Daniel Berlin
2004-03-15 21:00 ` Andrew MacLeod
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=1079374594.4007.3593.camel@p4 \
--to=amacleod@redhat.com \
--cc=dberlin@dberlin.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rth@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).