From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6740] Sparse fixes: add extern to ELF opcode tables to avoid warnings
Date: Sat, 07 Mar 2009 15:59:10 +0000 [thread overview]
Message-ID: <E1Lfyve-0008LC-5y@cvs.savannah.gnu.org> (raw)
Revision: 6740
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6740
Author: blueswir1
Date: 2009-03-07 15:59:09 +0000 (Sat, 07 Mar 2009)
Log Message:
-----------
Sparse fixes: add extern to ELF opcode tables to avoid warnings
Modified Paths:
--------------
trunk/target-ppc/translate.c
Modified: trunk/target-ppc/translate.c
===================================================================
--- trunk/target-ppc/translate.c 2009-03-07 15:53:15 UTC (rev 6739)
+++ trunk/target-ppc/translate.c 2009-03-07 15:59:09 UTC (rev 6740)
@@ -604,6 +604,7 @@
#if defined(DO_PPC_STATISTICS)
#define GEN_OPCODE(name, op1, op2, op3, invl, _typ) \
+extern opcode_t opc_##name; \
OPCODES_SECTION opcode_t opc_##name = { \
.opc1 = op1, \
.opc2 = op2, \
@@ -633,6 +634,7 @@
}
#else
#define GEN_OPCODE(name, op1, op2, op3, invl, _typ) \
+extern opcode_t opc_##name; \
OPCODES_SECTION opcode_t opc_##name = { \
.opc1 = op1, \
.opc2 = op2, \
@@ -646,6 +648,7 @@
.oname = stringify(name), \
}
#define GEN_OPCODE2(name, onam, op1, op2, op3, invl, _typ) \
+extern opcode_t opc_##name; \
OPCODES_SECTION opcode_t opc_##name = { \
.opc1 = op1, \
.opc2 = op2, \
@@ -661,6 +664,7 @@
#endif
#define GEN_OPCODE_MARK(name) \
+extern opcode_t opc_##name; \
OPCODES_SECTION opcode_t opc_##name = { \
.opc1 = 0xFF, \
.opc2 = 0xFF, \
reply other threads:[~2009-03-07 15:59 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=E1Lfyve-0008LC-5y@cvs.savannah.gnu.org \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).