public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Richard Sandiford <rsandifo@nildram.co.uk>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR35371 GCSE loses track of REG_POINTER attribute
Date: Tue, 26 Feb 2008 19:04:00 -0000	[thread overview]
Message-ID: <1204052325.7014.2.camel@otta> (raw)
In-Reply-To: <87skzfzkvh.fsf@firetop.home>

On Tue, 2008-02-26 at 17:29 +0000, Richard Sandiford wrote:
> Minor suggestion, but maybe this could go in emit-rtl.c, under a more
> generic name?  Given the performance impact of losing pointer info,
> it would be nice to have a defined API for creating a register that's
> like another.

Having tracked a similar problem in another file, I was thinking along
the same lines.  I'm bad at names though.  Care to suggest a name for
the new function?

Peter



  reply	other threads:[~2008-02-26 18:59 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 [this message]
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
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=1204052325.7014.2.camel@otta \
    --to=bergner@vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.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).