From: Andrew Cagney <ac131313@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [patch] Add PS_REGNUM.
Date: Sat, 06 Apr 2002 12:26:00 -0000 [thread overview]
Message-ID: <3CAF59CA.1060304@cygnus.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
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
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1210 bytes --]
2002-04-06 Andrew Cagney <ac131313@redhat.com>
* gdbarch.sh (PS_REGNUM): Add. Document. Default to -1.
* gdbarch.c, gdbarch.h: Re-generate.
Index: gdbarch.sh
===================================================================
RCS file: /cvs/src/src/gdb/gdbarch.sh,v
retrieving revision 1.122
diff -u -r1.122 gdbarch.sh
--- gdbarch.sh 2002/04/06 03:07:59 1.122
+++ gdbarch.sh 2002/04/06 20:17:23
@@ -431,9 +431,16 @@
# These pseudo-registers may be aliases for other registers,
# combinations of other registers, or they may be computed by GDB.
v:2:NUM_PSEUDO_REGS:int:num_pseudo_regs::::0:0::0:::
+
+# GDB's standard (or well known) register numbers. These can map onto
+# a real register or a pseudo (computed) register or not be defined at
+# all (-1). FIXME: cagney/2002-04-05: As of the time of writing, only
+# the PS_REGNUM was optional - code still depends on the others (fp,
+# pc, sp) designating registers.
v:2:SP_REGNUM:int:sp_regnum::::0:-1
v:2:FP_REGNUM:int:fp_regnum::::0:-1
v:2:PC_REGNUM:int:pc_regnum::::0:-1
+v:2:PS_REGNUM:int:ps_regnum::::-1:-1::0
v:2:FP0_REGNUM:int:fp0_regnum::::0:-1::0
v:2:NPC_REGNUM:int:npc_regnum::::0:-1::0
v:2:NNPC_REGNUM:int:nnpc_regnum::::0:-1::0
next reply other threads:[~2002-04-06 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 12:26 Andrew Cagney [this message]
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
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=3CAF59CA.1060304@cygnus.com \
--to=ac131313@cygnus.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