From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: Dale Johannesen <dalej@apple.com>
Cc: "gcc@gcc.gnu.org list" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa vs lno] who is right?
Date: Fri, 26 Mar 2004 18:51:00 -0000 [thread overview]
Message-ID: <20040326181034.GA24586@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <086B964A-7EC5-11D8-8C7F-000A95D7CD40@apple.com>
Hello,
> When the LNO branch copies a loop, it attempts to fix up the phi nodes
> with
> an algorithm that assumes there is only one phi per block per variable.
> That is, it
> won't see code like this:
where do we assume this (i.e. what do you mean by "copying a loop")?
While this certainly is unlikely to happen, there probably is nothing
that would prevent it.
Zdenek
> ;; 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).
>
next prev parent reply other threads:[~2004-03-26 18:10 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
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 [this message]
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=20040326181034.GA24586@atrey.karlin.mff.cuni.cz \
--to=rakdver@atrey.karlin.mff.cuni.cz \
--cc=dalej@apple.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).