From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [obish] -Wunused-function warnings
Date: Mon, 19 Jan 2004 23:14:00 -0000 [thread overview]
Message-ID: <20040119161445.3ff57ba5@saguaro> (raw)
In-Reply-To: <400C227B.9040704@gnu.org>
On Mon, 19 Jan 2004 13:31:23 -0500
Andrew Cagney <cagney@gnu.org> wrote:
> Here's this week's list. It's noticably shorter, and core-GDB items
> still remaining have been figured out. Again, can I encourage
> architecture maintainers to check this out.
I've taken care of the unused declarations in frv-tdep.c. I've just
committed the following patch:
* frv-tdep.c (frv_push_arguments, frv_saved_pc_after_call): Delete
unused declarations.
Index: frv-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/frv-tdep.c,v
retrieving revision 1.66
diff -u -p -r1.66 frv-tdep.c
--- frv-tdep.c 17 Jan 2004 15:34:11 -0000 1.66
+++ frv-tdep.c 19 Jan 2004 23:09:18 -0000
@@ -44,8 +44,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 gdbarch_frameless_function_invocation_ftype frv_frameless_function_invocation;
-static gdbarch_deprecated_push_arguments_ftype frv_push_arguments;
-static gdbarch_deprecated_saved_pc_after_call_ftype frv_saved_pc_after_call;
/* Register numbers. The order in which these appear define the
remote protocol, so take care in changing them. */
next prev parent reply other threads:[~2004-01-19 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 18:26 Andrew Cagney
2004-01-12 2:05 ` Daniel Jacobowitz
2004-01-12 14:58 ` Andrew Cagney
2004-01-15 18:46 ` Elena Zannoni
2004-01-17 1:04 ` [commit] rm unused symtab & sh functions; Was: " Andrew Cagney
2004-01-19 18:31 ` Andrew Cagney
2004-01-19 23:14 ` Kevin Buettner [this message]
2004-01-19 23:21 ` Kevin Buettner
2004-02-03 22:23 ` Andrew Cagney
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=20040119161445.3ff57ba5@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