From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] minor frv-tdep.c cleanups
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040315113436.041ccd4c@saguaro> (raw)
Message-ID: <20040319000900.lMR38tUIeQzVUI174SwIzv_DPrOV2PzjIKm0FMGHcm0@z> (raw)
I've committed the patch below...
* frv-tdep.c (frv_call_dummy_words): Delete.
(frv_frame_unwind_cache): Delete unused variable, ``prev_sp''.
Index: frv-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/frv-tdep.c,v
retrieving revision 1.76
diff -u -p -r1.76 frv-tdep.c
--- frv-tdep.c 13 Mar 2004 01:24:20 -0000 1.76
+++ frv-tdep.c 15 Mar 2004 18:29:10 -0000
@@ -48,9 +48,6 @@ static gdbarch_breakpoint_from_pc_ftype
static gdbarch_adjust_breakpoint_address_ftype frv_gdbarch_adjust_breakpoint_address;
static gdbarch_skip_prologue_ftype frv_skip_prologue;
-static LONGEST frv_call_dummy_words[] =
-{0};
-
struct frv_unwind_cache /* was struct frame_extra_info */
{
@@ -65,7 +62,6 @@ struct frv_unwind_cache /* was struct f
struct trad_frame_saved_reg *saved_regs;
};
-
/* A structure describing a particular variant of the FRV.
We allocate and initialize one of these structures when we create
the gdbarch object for a variant.
@@ -925,7 +921,6 @@ frv_frame_unwind_cache (struct frame_inf
{
struct gdbarch *gdbarch = get_frame_arch (next_frame);
CORE_ADDR pc;
- ULONGEST prev_sp;
ULONGEST this_base;
struct frv_unwind_cache *info;
next reply other threads:[~2004-03-15 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 18:34 Kevin Buettner [this message]
2004-03-19 0:09 ` Kevin Buettner
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=20040315113436.041ccd4c@saguaro \
--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