Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Add PS_REGNUM.
Date: Sun, 07 Apr 2002 14:12:00 -0000	[thread overview]
Message-ID: <20020407171216.A30655@nevyn.them.org> (raw)
In-Reply-To: <3CB0B559.3000306@cygnus.com>

On Sun, Apr 07, 2002 at 05:08:41PM -0400, Andrew Cagney wrote:
> >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.
> >
> >
> >So what you're saying is that you added PS_REGNUM so that it could be
> >used as a standard $ps register name, not for the rest of GDB, right?
> 
> Yes.  And that is how FP_REGNUM et.al. should be used ....

Completely agree.

> >I don't really see the point; anyone who wants to look at the processor
> >status register presumably knows what some of the bits in it mean,
> >which is entirely architecture dependant.  But caveat implementor :)
> 
> Who am I to argue with the documentation :-)

Didn't know it was there, but now I see it.  So true... :)

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-04-07 21:12 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
2002-04-07 13:59     ` Daniel Jacobowitz
2002-04-07 14:08       ` Andrew Cagney
2002-04-07 14:12         ` Daniel Jacobowitz [this message]

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=20020407171216.A30655@nevyn.them.org \
    --to=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