From: Jeff Law <law@redhat.com>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: Richard Sandiford <rsandifo@nildram.co.uk>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"H.J. Lu" <hjl@lucon.org>
Subject: Re: [PATCH] PR35371 GCSE loses track of REG_POINTER attribute
Date: Mon, 03 Mar 2008 19:17:00 -0000 [thread overview]
Message-ID: <47CC4E4D.5040706@redhat.com> (raw)
In-Reply-To: <1204240130.7376.16.camel@otta>
Peter Bergner wrote:
> On Tue, 2008-02-26 at 12:25 -0700, Jeff Law wrote:
>> If someone wanted to get real ambitious they could revamp the
>> REG_POINTER propagation code as well. It's amazingly simplistic
>> at the moment (see regclass.c:reg_scan_mark_refs). Basically it
>> fails to propagate for any register destination that is set more
>> than once, even if all the sets are of the proper form for
>> propagating REG_POINTER.
>
> Do you mean fix it up and then call it from more than just CSE?
> Currently, the only call to reg_scan() isn't in a location that
> will help me.
No. I mean make it smarter. If you read the code it's amazingly
simplistic and punts propagation of REG_POINTER for any pseudo
that is set more than once.
It shouldn't be terribly difficult to build a simple propagation
engine that handles multiple sets.
Jeff
next prev parent reply other threads:[~2008-03-03 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:30 Peter Bergner
2008-02-25 23:13 ` Peter Bergner
2008-02-26 5:25 ` [PATCH,updated] " Peter Bergner
2008-02-26 5:49 ` [PATCH,withdrawn] " Peter Bergner
2008-02-26 18:00 ` [PATCH] " Richard Sandiford
2008-02-26 19:04 ` Peter Bergner
2008-02-26 19:45 ` Richard Sandiford
2008-02-26 20:06 ` Jeff Law
2008-02-29 1:32 ` Peter Bergner
2008-03-03 19:17 ` Jeff Law [this message]
2008-03-03 19:42 ` Peter Bergner
2008-03-03 20:55 ` Jeff Law
2008-03-10 15:32 ` [PING H.J. Lu] " Peter Bergner
2008-03-10 16:22 ` H.J. Lu
2008-03-12 14:48 ` H.J. Lu
2008-03-17 14:32 ` H.J. Lu
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=47CC4E4D.5040706@redhat.com \
--to=law@redhat.com \
--cc=bergner@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=rsandifo@nildram.co.uk \
/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).