Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: handle missing fpregs
Date: Fri, 07 May 2004 22:56:00 -0000	[thread overview]
Message-ID: <20040507155610.43b806ff@saguaro> (raw)
In-Reply-To: <vt2pt9gx81k.fsf@zenia.home>

On 07 May 2004 16:05:11 -0500
Jim Blandy <jimb@redhat.com> wrote:

> > > +     /* On RS6000 variants that have no floating-point registers, the
> > > +        next two members will be -1.  */
> > 
> > I'm not comfortable with the term "RS6000 variants" here.  I'd be happier
> > with "PPC variants", though that's probably not strictly correct either.
> > I suppose you could just say "On cores that have no floating-point
> > registers...".
> 
> The issue is that people might not immediately see all PPC's as RS6000
> variants, right?  Fair enough.  "RS6000 variants" is historically
> correct, but it's not like anyone has fabricated an RS6000 in recent
> history.  I've changed that to "On PPC and RS6000 variants that ...".

Okay, that's fine.

Your revised patch is okay to commit.

Thanks!

Kevin


  reply	other threads:[~2004-05-07 22:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07  1:19 Jim Blandy
2004-05-07 11:20 ` Mark Kettenis
2004-05-07 20:54   ` Jim Blandy
2004-05-07 20:18 ` Kevin Buettner
2004-05-07 21:09   ` Jim Blandy
2004-05-07 22:56     ` Kevin Buettner [this message]
2004-05-10 17:08       ` Jim Blandy
2004-05-10 19:00       ` Jim Blandy
     [not found]         ` <D567851C-A2B8-11D8-94E3-000A957650EC@wasabisystems.com>
2004-05-10 22:16           ` Jim Blandy
2004-05-10 22:28             ` Jason Thorpe
2004-05-11  4:55               ` Jim Blandy

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=20040507155610.43b806ff@saguaro \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    /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