Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Add PS_REGNUM.
Date: Sun, 07 Apr 2002 11:54:00 -0000	[thread overview]
Message-ID: <3CB095CA.6090405@cygnus.com> (raw)
In-Reply-To: <20020407143417.A26612@nevyn.them.org>

> On Sat, Apr 06, 2002 at 03:25:46PM -0500, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> This patch just fills in a gap in the current *_REGNUMs by adding 
>> PS_REGNUM.  Unlike the others.  This one really does allow -1 as the 
>> default value.
>> 
>> (FP_REGNUM et.al. require real values as there is code around that, 
>> unfortunatly, depends on there being a real FP register et.al.  ulgh).
>> 
>> committed,
>> Andrew
> 
> 
> What benefit does this have?  PC_REGNUM I can understand.  Even
> SP_REGNUM.  But it's not like PS_REGNUM has any meaning to common
> code...

I think it is the other way round.  PS_REGNUM is the only one being used 
correctly - when >=0, std-regs.c (new file) maps $ps onto a 
hardware/pseudo register.  Cf the GDB manual.

On the other hand FP_REGNUM, PC_REGNUM and SP_REGNUM that are being used 
``incorrectly''(1).  They have no meaning outside of std-regs.c yet are 
used throughout GDB.

enjoy,
Andrew

(1) I'm rewriting history here.  There was a time when the FP_REGNUM was 
both a hardware register and the frame-base.


  reply	other threads:[~2002-04-07 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 12:26 Andrew Cagney
2002-04-07 11:35 ` Daniel Jacobowitz
2002-04-07 11:54   ` Andrew Cagney [this message]
2002-04-07 13:59     ` Daniel Jacobowitz
2002-04-07 14:08       ` Andrew Cagney
2002-04-07 14:12         ` Daniel Jacobowitz

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=3CB095CA.6090405@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@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