Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Re: PowerPC 603 Register Set Clarification
Date: Thu, 27 Oct 2005 15:35:00 -0000	[thread overview]
Message-ID: <20051027153545.GA25150@nevyn.them.org> (raw)
In-Reply-To: <20051027025856.GD6186@Power-Mac-G5.local>

On Wed, Oct 26, 2005 at 10:58:56PM -0400, Ron McCall wrote:
> Hi,
> 
> I am unsure as to how to handle the ASR register and the two placeholder
> registers that are defined for the PowerPC 603 with respect to the 'g'
> and 'G' packets and was hoping someone could clarify it for me.  I am
> currently working with GDB 6.3.50.20051026.
> 
> In rs6000-tdep.c, PPC_OEA_SPRS includes the ASR register which is
> declared S64 (a 64-bit register on 64-bit systems that doesn't exist on
> 32-bit systems).  The 603 isn't 64-bit but the register still appears to
> take up a register number nonetheless.  Does it also take up space (16
> hex chars) in the 'G' packet, which is then intended to be skipped by
> the stub?  If so, should the stub then fill in zeroes for this register
> in the 'g' packet?

The best way to answer this question is to configure GDB appropriately
to talk to a 603 target, and then run "maint info registers".  That
will tell you the expected offsets of every register.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-10-27 15:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27  2:59 Ron McCall
2005-10-27 15:35 ` Daniel Jacobowitz [this message]
2005-10-27 18:30   ` Ron McCall
2005-10-27 18:35     ` Daniel Jacobowitz
2005-10-27 19:08       ` Ron McCall

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=20051027153545.GA25150@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.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