From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com
Subject: another opcodes warning fix
Date: Fri, 19 Nov 2004 12:39:00 -0000 [thread overview]
Message-ID: <20041119123858.GF7749@bubble.modra.org> (raw)
* or32-opc.c (debug): Warning fix.
* po/POTFILES.in: Regenerate.
Index: opcodes/or32-opc.c
===================================================================
RCS file: /cvs/src/src/opcodes/or32-opc.c,v
retrieving revision 1.2
diff -u -p -r1.2 or32-opc.c
--- opcodes/or32-opc.c 8 Feb 2002 12:12:15 -0000 1.2
+++ opcodes/or32-opc.c 19 Nov 2004 11:04:31 -0000
@@ -345,10 +345,8 @@ const struct or32_opcode or32_opcodes[]
static void debug PARAMS ((int, const char *, ...));
static void
-debug (int level, const char *format, ...)
+debug (int level ATTRIBUTE_UNUSED, const char *format ATTRIBUTE_UNUSED, ...)
{
- /* Just to get rid of warnings. */
- format = (char *) level = 0;
}
#endif
Index: opcodes/po/POTFILES.in
===================================================================
RCS file: /cvs/src/src/opcodes/po/POTFILES.in,v
retrieving revision 1.29
diff -u -p -r1.29 POTFILES.in
--- opcodes/po/POTFILES.in 17 Sep 2004 06:13:39 -0000 1.29
+++ opcodes/po/POTFILES.in 19 Nov 2004 11:04:33 -0000
@@ -88,6 +88,7 @@ m68hc11-opc.c
m68k-dis.c
m68k-opc.c
m88k-dis.c
+maxq-dis.c
mcore-dis.c
mcore-opc.h
mips16-opc.c
--
Alan Modra
IBM OzLabs - Linux Technology Centre
reply other threads:[~2004-11-19 12: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=20041119123858.GF7749@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@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).