From: Daniel Berlin <dberlin@dberlin.org>
To: Diego Novillo <dnovillo@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Andrew Macleod <amacleod@redhat.com>
Subject: Re: [PATCH]: Implement must-def kill operand
Date: Wed, 20 Oct 2004 17:56:00 -0000 [thread overview]
Message-ID: <EB4A19C4-22C0-11D9-B310-000D93B1B044@dberlin.org> (raw)
In-Reply-To: <1098293613.22552.36.camel@localhost.localdomain>
On Oct 20, 2004, at 1:33 PM, Diego Novillo wrote:
> On Sun, 2004-10-17 at 22:00, Daniel Berlin wrote:
>
>> This is a revision of the previous patch, the main change is that it
>> no
>> longer requires DCE to go into and out of SSA to rename the virtual
>> must-def operands, as Andrew requested. The renaming it does
>> in DCE is just the 3rd phase of the regular renamer (rewriting
>> reaching
>> definitions),
>>
> I would rather parameterize the renamer to deal with this situation.
> Just to make sure I understood the problem and the IRC discussion.
> Here
> we have the following situation:
>
> # A_4 = V_MUST_DEF <A_3>
> 1. A = ...;
>
> # A_5 = V_MUST_DEF <A_4>
> 2. A = ...;
>
> A_4 is dead because no statement uses A_4 (the RHS of a V_MUST_DEF is
> not a use, it only specifies which version is this V_MUST_DEF killing).
> Once we remove statement (1), we need to tell statement (2) that it no
> longer kills A_4, it now kills whichever version was left dominating it
> (it may or may not be A_3).
>
Right.
> What we need here is a regular renaming pass, but not all of it. We
> only need to (a) detect def sites, (b) walk the dominator the dominator
> tree rewriting the operands of V_MUST_DEFs with CURRENT_DEF. That is,
> we need to skip the PHI insertion phase.
Okay.
>
> So, I guess this involves a new TODO_* flag (TODO_fix_def_def_chains?)
> which does (a) and (b) using the existing renamer. The additional
> logic
> in the renamer should not slow it down one bit, nor make it more
> complicated to follow.
I'll implement this and repost the patch.
I assume nobody really had much problem with the *other* parts of the
patch?
> Diego.
>
next prev parent reply other threads:[~2004-10-20 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 2:29 Daniel Berlin
2004-10-20 17:41 ` Diego Novillo
2004-10-20 17:56 ` Daniel Berlin [this message]
2004-10-20 18:08 ` Diego Novillo
2004-10-20 18:28 ` Daniel Berlin
2004-10-20 20:36 ` Diego Novillo
2004-10-20 20:49 ` Daniel Berlin
2004-10-20 20:57 ` Diego Novillo
2004-10-20 21:01 ` Daniel Berlin
[not found] ` <531813B6-22DA-11D9-B310-000D93B1B044@dberlin.org>
2004-10-20 21:04 ` Diego Novillo
2004-10-20 21:27 ` Daniel Berlin
2004-10-20 22:23 ` Andrew Pinski
2004-10-23 5:02 ` Mark Mitchell
2004-10-23 12:56 ` Diego Novillo
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=EB4A19C4-22C0-11D9-B310-000D93B1B044@dberlin.org \
--to=dberlin@dberlin.org \
--cc=amacleod@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc-patches@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).