From: Daniel Berlin <dberlin@dberlin.org>
To: law@redhat.com
Cc: dnovillo@redhat.com, gcc-patches@gcc.gnu.org,
amacleod@redhat.com, Steven Bosscher <stevenb@suse.de>
Subject: Re: Fix a tcb crash and a potential bug on mainline
Date: Tue, 19 Oct 2004 22:27:00 -0000 [thread overview]
Message-ID: <896EAE9A-221D-11D9-9D21-000A95DA505C@dberlin.org> (raw)
In-Reply-To: <1098223558.2915.131.camel@localhost.localdomain>
>
>>
>>>> This may be something Andrew may want to look into as part
>>>> of his immediate uses work??
>>>
>>> It's something we've pondered and talked about a little. Basically
>>> with the immediate use work we would know where all the uses are
>>> and we could probably arrange to delete those uses.
>>
>> How would you delete those uses? You don't know if those statements
>> are dead, so you really can't do that.
> If they are using the result of a deleted PHI or some other deleted
> statement, then those statements must also be dead. It's one of
> the nice SSA properties.
>
Only if your pass performs *all* insertions and updates to statements
before performing *any* removals of statements.
I believe some passes don't do this right now.
Otherwise, in the intermediate step, we would think some statements are
dead when they are only dead because we haven't fixed them up yet :)
--Dan
next prev parent reply other threads:[~2004-10-19 22:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 21:09 Steven Bosscher
2004-10-18 22:06 ` Andrew MacLeod
2004-10-18 22:18 ` Andrew Pinski
2004-10-19 20:58 ` Jeffrey A Law
2004-10-19 21:29 ` Steven Bosscher
2004-10-19 22:08 ` Jeffrey A Law
2004-10-19 22:27 ` Daniel Berlin [this message]
2004-10-19 22:35 ` Jeffrey A Law
2004-10-19 23:08 ` Daniel Berlin
2004-10-19 23:14 ` Daniel Berlin
2004-10-21 2:33 ` Jeffrey A Law
2004-10-19 22:36 ` Steven Bosscher
2004-10-19 22:41 ` Diego Novillo
2004-10-19 23:16 ` Jeffrey A Law
2004-10-20 13:17 ` Andrew MacLeod
2004-10-20 13:32 ` Steven Bosscher
2004-10-20 13:47 ` Andrew MacLeod
2004-10-20 14:30 ` Steven Bosscher
2004-10-20 16:53 ` Andrew MacLeod
2004-10-20 17:33 ` Daniel Berlin
2004-10-22 19:15 ` Jeffrey A Law
2004-10-22 19:33 ` Steven Bosscher
2004-10-22 19:37 ` Jeffrey A Law
2004-10-22 19:40 ` Steven Bosscher
2004-10-22 21:08 ` Jeffrey A Law
2004-10-24 21:20 ` Steven Bosscher
2004-10-27 16:27 ` Jeffrey A Law
2004-10-22 19:10 ` Jeffrey A Law
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=896EAE9A-221D-11D9-9D21-000A95DA505C@dberlin.org \
--to=dberlin@dberlin.org \
--cc=amacleod@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=stevenb@suse.de \
/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).