From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Multiarch FRAME_INIT_SAVED_REGS for mips
Date: Thu, 08 Aug 2002 16:36:00 -0000 [thread overview]
Message-ID: <1020808233610.ZM25838@localhost.localdomain> (raw)
I've just committed the patch below.
* mips-tdep.c (mips_find_saved_regs): Make static.
(mips_frame_init_saved_regs): New function.
(mips_gdbarch_init): Setup FRAME_INIT_SAVED_REGS method.
* config/mips/tm-mips.h (FRAME_INIT_SAVED_REGS): Delete macro.
(mips_find_saved_regs): Delete declaration.
Index: mips-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/mips-tdep.c,v
retrieving revision 1.92
diff -u -p -r1.92 mips-tdep.c
--- mips-tdep.c 8 Aug 2002 00:26:51 -0000 1.92
+++ mips-tdep.c 8 Aug 2002 23:26:16 -0000
@@ -1259,7 +1259,7 @@ mips_next_pc (CORE_ADDR pc)
/* Guaranteed to set fci->saved_regs to some values (it never leaves it
NULL). */
-void
+static void
mips_find_saved_regs (struct frame_info *fci)
{
int ireg;
@@ -1437,6 +1437,23 @@ mips_find_saved_regs (struct frame_info
fci->saved_regs[PC_REGNUM] = fci->saved_regs[RA_REGNUM];
}
+/* Set up the 'saved_regs' array. This is a data structure containing
+ the addresses on the stack where each register has been saved, for
+ each stack frame. Registers that have not been saved will have
+ zero here. The stack pointer register is special: rather than the
+ address where the stack register has been saved, saved_regs[SP_REGNUM]
+ will have the actual value of the previous frame's stack register. */
+
+static void
+mips_frame_init_saved_regs (struct frame_info *frame)
+{
+ if (frame->saved_regs == NULL)
+ {
+ mips_find_saved_regs (frame);
+ }
+ frame->saved_regs[SP_REGNUM] = frame->frame;
+}
+
static CORE_ADDR
read_next_frame_reg (struct frame_info *fi, int regno)
{
@@ -4715,6 +4732,7 @@ mips_gdbarch_init (struct gdbarch_info i
/* Initialize a frame */
set_gdbarch_init_extra_frame_info (gdbarch, mips_init_extra_frame_info);
+ set_gdbarch_frame_init_saved_regs (gdbarch, mips_frame_init_saved_regs);
/* MIPS version of CALL_DUMMY */
Index: config/mips/tm-mips.h
===================================================================
RCS file: /cvs/src/src/gdb/config/mips/tm-mips.h,v
retrieving revision 1.29
diff -u -p -r1.29 tm-mips.h
--- config/mips/tm-mips.h 8 Aug 2002 22:44:46 -0000 1.29
+++ config/mips/tm-mips.h 8 Aug 2002 23:26:16 -0000
@@ -304,19 +304,6 @@ extern int mips_frame_num_args (struct f
#define FRAME_ARGS_SKIP 0
-/* Put here the code to store, into a struct frame_saved_regs,
- the addresses of the saved registers of frame described by FRAME_INFO.
- This includes special registers such as pc and fp saved in special
- ways in the stack frame. sp is even more special:
- the address we return for it IS the sp for the next frame. */
-
-#define FRAME_INIT_SAVED_REGS(frame_info) \
- do { \
- if ((frame_info)->saved_regs == NULL) \
- mips_find_saved_regs (frame_info); \
- (frame_info)->saved_regs[SP_REGNUM] = (frame_info)->frame; \
- } while (0)
-extern void mips_find_saved_regs (struct frame_info *);
\f
/* Things needed for making the inferior call functions. */
reply other threads:[~2002-08-08 23:36 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=1020808233610.ZM25838@localhost.localdomain \
--to=kevinb@redhat.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