public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org> To: Andrew MacLeod <amacleod@redhat.com> 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:52:00 -0000 [thread overview] Message-ID: <Pine.LNX.4.56.0403151349330.11905@dberlin.org> (raw) In-Reply-To: <1079375452.4011.3597.camel@p4> On Mon, 15 Mar 2004, Andrew MacLeod wrote: > On Mon, 2004-03-15 at 13:27, Daniel Berlin wrote: > > > > > > > > > Before the transformation, you have: > > T.6<D1061>_13 = k<D1047>_26 * 4; > > ... > > T.2<D1056>_42 = T.1<D1055>_41 * 4; > > > > one lexical occurrence of k * 4, one lexical occurrence of T.1 * 4. > > > > after, you have > > <L0>:; > > T.6<D1061>_13 = k<D1047>_26 * 4; > > ... > > T.2<D1056>_42 = k<D1047>_41 * 4; > > > > two lexical occurrences of k * 4. > > > > even tho k_41 has absolutely nothing to do with the 'k' in k_26 eh. yes. Braindead, i know. This isn't as big a problem in other compilers because they don't have as many different named temporaries for variables. IE copyrename should improve PRE effectiveness in a lot of cases, at least until we have GVN-PRE. > > I looked at the code PRE generates for optimizing that expression by eye, > > and it looks okay to me. > > OK, I'll see if I can see anyone else doing something bad then. someone > is getting confused :-) :P It still could be PRE, and i'm just missing it. But i traced the replacements it made by hand, and looked at the resulting code, and it looks like it should be okay.
next prev parent reply other threads:[~2004-03-15 18:52 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 2004-03-15 18:27 ` Daniel Berlin 2004-03-15 18:31 ` Andrew MacLeod 2004-03-15 18:52 ` Daniel Berlin [this message] 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=Pine.LNX.4.56.0403151349330.11905@dberlin.org \ --to=dberlin@dberlin.org \ --cc=amacleod@redhat.com \ --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: linkBe 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).