public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dale Johannesen <dalej@apple.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: "gcc@gcc.gnu.org list" <gcc@gcc.gnu.org>,
	Dale Johannesen <dalej@apple.com>
Subject: Re: [tree-ssa vs lno] who is right?
Date: Fri, 26 Mar 2004 06:35:00 -0000	[thread overview]
Message-ID: <045E0A00-7EC9-11D8-8C7F-000A95D7CD40@apple.com> (raw)
In-Reply-To: <1080264779.4600.25.camel@localhost.localdomain>


On Mar 25, 2004, at 5:32 PM, Diego Novillo wrote:

> On Thu, 2004-03-25 at 20:29, Dale Johannesen wrote:
>
>> ;; basic block 19, loop depth 0, count 0
>> ;; prev block 9, next block 20
>> ;; pred:       10 [100.0%]  (fallthru)
>> ;; succ:       28 [50.0%]  (true,exec) 29 [50.0%]  (false,exec)
>> # maxmin_Result_140 = PHI <1(10)>;
>> # maxmin_Result_142 = PHI <2(10)>;
>> # lsm_tmp.19_144 = PHI <lsm_tmp.19_84(10)>;
>> <L28>:;
>> if (m__10 == 0) goto <L26>; else goto <L27>;
>>
>> Is that suppose to be a valid assumption?  The dup is created by
>> copyrename, and
>> I see no code there that's intended to stop dups from being created 
>> (on
>> the
>> contrary, but surely it's unusual for the live ranges to overlap).

Thanks.

> Are maxmin_Result the same variable?  Use -uid to find out.

How?  Doesn't like that as a command line option...

> If they both have the same UID, they're the same and that's a bug.  
> There should
> only be a single PHI node per variable in a basic block.

They are the same VAR_DECL (pointed to from different SSA_NAMEs).
Is it one of the UIDs in there that matters, or the one in the PHI?

  reply	other threads:[~2004-03-26  1:58 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 [this message]
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
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=045E0A00-7EC9-11D8-8C7F-000A95D7CD40@apple.com \
    --to=dalej@apple.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.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).