From: Kevin Buettner <kevinb@redhat.com>
To: rda@sources.redhat.com
Subject: [PATCH] Add/fix support of MIPS "fir"/"fsr" registers
Date: Thu, 10 Apr 2003 20:39:00 -0000 [thread overview]
Message-ID: <1030410203928.ZM8838@localhost.localdomain> (raw)
I've just committed that patch below.
* linux-target.c (NUM_REGS) [MIPS_LINUX_TARGET, MIPS64_LINUX_TARGET]:
Bump to 72.
(struct peekuser_pokeuser_reginfo) [MIPS_LINUX_TARGET]: Use
PROTO_SIZE for ``bad'' and ``cause''.
(struct peekuser_pokeuser_reginfo) [MIPS_LINUX_TARGET]
[MIPS64_LINUX_TARGET]: Add ``fir'' register.
Index: linux-target.c
===================================================================
RCS file: /cvs/src/src/rda/unix/linux-target.c,v
retrieving revision 1.5
diff -u -p -r1.5 linux-target.c
--- linux-target.c 7 Feb 2003 23:03:08 -0000 1.5
+++ linux-target.c 10 Apr 2003 20:06:32 -0000
@@ -385,7 +385,7 @@ is_extended_reg (int regnum)
enum
{
- NUM_REGS = 70,
+ NUM_REGS = 72,
PC_REGNUM = 37,
sign_extend = 1
};
@@ -478,8 +478,8 @@ static struct peekuser_pokeuser_reginfo
{ BADVADDR, 4, GREGS, 35 * 4, 4, PROTO_SIZE }, /* bad */
{ CAUSE, 4, GREGS, 36 * 4, 4, PROTO_SIZE }, /* cause */
#else
- { 0, 8, NOREGS, 0, 8, 8 }, /* bad */
- { 0, 8, NOREGS, 0, 8, 8 }, /* cause */
+ { 0, 8, NOREGS, 0, 8, PROTO_SIZE }, /* bad */
+ { 0, 8, NOREGS, 0, 8, PROTO_SIZE }, /* cause */
#endif
{ PC, 4, GREGS, 34 * 4, 4, PROTO_SIZE }, /* pc */
@@ -522,7 +522,10 @@ static struct peekuser_pokeuser_reginfo
{ FPR_BASE + 29, 4, FPREGS, 29 * 4, 4, PROTO_SIZE }, /* $f29 */
{ FPR_BASE + 30, 4, FPREGS, 30 * 4, 4, PROTO_SIZE }, /* $f30 */
{ FPR_BASE + 31, 4, FPREGS, 31 * 4, 4, PROTO_SIZE }, /* $f31 */
- { FPC_CSR, 4, FPREGS, 64 * 4, 4, PROTO_SIZE } /* fsr */
+ { FPC_CSR, 4, FPREGS, 64 * 4, 4, PROTO_SIZE }, /* fsr */
+ /* The "fir" value actually ends up occupying fp_pad in the fpregset
+ struct. */
+ { FPC_EIR, 4, FPREGS, 65 * 4, 4, PROTO_SIZE } /* fir */
};
static void mips_singlestep_program (struct gdbserv *serv);
@@ -535,7 +538,7 @@ static void mips_singlestep_program (str
enum
{
- NUM_REGS = 70,
+ NUM_REGS = 72,
PC_REGNUM = 37,
sign_extend = 1
};
@@ -642,7 +645,10 @@ static struct peekuser_pokeuser_reginfo
{ 32 + 29, 8, FPREGS, 29 * 8, 8, 8 }, /* $f29 */
{ 32 + 30, 8, FPREGS, 30 * 8, 8, 8 }, /* $f30 */
{ 32 + 31, 8, FPREGS, 31 * 8, 8, 8 }, /* $f31 */
- { 69, 4, FPREGS, 32 * 8, 4, 8 } /* fsr */
+ { 69, 8, FPREGS, 32 * 8, 4, 8 }, /* fsr */
+ /* The "fir" value actually ends up occupying fp_pad in the fpregset
+ struct. */
+ { 70, 8, FPREGS, 33 * 8 + 4, 4, 8} /* fir */
};
static void mips_singlestep_program (struct gdbserv *serv);
reply other threads:[~2003-04-10 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1030410203928.ZM8838@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=rda@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).