Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Jim Blandy <jimb@redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: PowerPC sim & GDB: use fixed register numbering
Date: Wed, 04 Aug 2004 17:33:00 -0000	[thread overview]
Message-ID: <41111DEC.7080102@gnu.org> (raw)
In-Reply-To: <vt2vffyde1a.fsf@zenia.home>

> Andrew Cagney <cagney@gnu.org> writes:
> 
>>>> > Andrew Cagney <cagney@gnu.org> writes:
>>>> >
>>>
>>>>>> >>> Have a look at the other sim-*.h files, you'll notice that most define
>>>>>> >>> an enum namespace and not a series of magic constants.   Can we expand
>>>>>> >>> the table so that the constants aren't needed?
>>>
>>>> > Is this going in the right direction?
>>
>>> 
>>> Yes, that should go in.
> 
> 
> Okay, committed.  Thanks to you and Kevin for the review.

Ok,

> The old code, which did an under-the-covers call into gdb to map number -> name, was bad and definitly needed to be replaced.  The above though could still do with some work - too much on the magic of those numbers in gdb/sim-ppc.h :-(
> 
> Anyway, lets first get the enum in place. 

Since we've nailed the enum, what should we do about the sim/ppc?

>>> What's your plan with SPRs?
> 
> 
> I think it's best to use the SPR numbers assigned by the ISA to
> identify them.  Trying to keep tables based on automatically assigned
> enum values in sync would take a lot of work, for little gain, since
> ISA SPR numbers are (obviously) unambiguous within any particular PPC
> variant.

Which is a change from the status quo.  That was doing things based on 
the ISA's register name.  Which ever.

> At the moment, the sim doesn't support any SPRs from different PPC
> variants whose numbers clash.  There'll be work needed there to handle
> that; I don't have any particular insights there.

Andrew


  reply	other threads:[~2004-08-04 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 20:40 Jim Blandy
2004-07-23 23:12 ` Kevin Buettner
2004-08-03 14:23 ` Andrew Cagney
2004-08-04  5:47   ` Jim Blandy
2004-08-04 13:53     ` Andrew Cagney
2004-08-04 17:13       ` Jim Blandy
2004-08-04 17:33         ` Andrew Cagney [this message]
2004-08-04 17:56           ` Jim Blandy
2004-08-04 18:07             ` Andrew Cagney
2004-08-04 21:26               ` Jim Blandy
2004-08-05  0:18                 ` Andrew Cagney
2004-08-05 15:22                   ` Jim Blandy
2004-08-05 16:10                     ` Andrew Cagney

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=41111DEC.7080102@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=kevinb@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