From: Hans de Goede <hdegoede@redhat.com>
To: qemu-devel@nongnu.org
Cc: Hans de Goede <hdegoede@redhat.com>
Subject: [Qemu-devel] [PATCH] Fix a number of unused-but-set-variable warnings (new with gcc-4.6)
Date: Tue, 3 May 2011 13:03:40 +0200 [thread overview]
Message-ID: <1304420620-8409-1-git-send-email-hdegoede@redhat.com> (raw)
---
target-i386/kvm.c | 4 ++--
tcg/tcg.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index a13599d..e9e8d54 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -950,7 +950,7 @@ static int kvm_get_xsave(CPUState *env)
#ifdef KVM_CAP_XSAVE
struct kvm_xsave* xsave;
int ret, i;
- uint16_t cwd, swd, twd, fop;
+ uint16_t cwd, swd, twd;
if (!kvm_has_xsave()) {
return kvm_get_fpu(env);
@@ -966,7 +966,7 @@ static int kvm_get_xsave(CPUState *env)
cwd = (uint16_t)xsave->region[0];
swd = (uint16_t)(xsave->region[0] >> 16);
twd = (uint16_t)xsave->region[1];
- fop = (uint16_t)(xsave->region[1] >> 16);
+ /* fop = (uint16_t)(xsave->region[1] >> 16); */
env->fpstt = (swd >> 11) & 7;
env->fpus = swd;
env->fpuc = cwd;
diff --git a/tcg/tcg.c b/tcg/tcg.c
index 8748c05..11a8daf 100644
--- a/tcg/tcg.c
+++ b/tcg/tcg.c
@@ -585,7 +585,7 @@ void tcg_register_helper(void *func, const char *name)
void tcg_gen_callN(TCGContext *s, TCGv_ptr func, unsigned int flags,
int sizemask, TCGArg ret, int nargs, TCGArg *args)
{
-#ifdef TCG_TARGET_I386
+#if defined TCG_TARGET_I386 && TCG_TARGET_REG_BITS < 64
int call_type;
#endif
int i;
@@ -612,7 +612,7 @@ void tcg_gen_callN(TCGContext *s, TCGv_ptr func, unsigned int flags,
*gen_opc_ptr++ = INDEX_op_call;
nparam = gen_opparam_ptr++;
-#ifdef TCG_TARGET_I386
+#if defined TCG_TARGET_I386 && TCG_TARGET_REG_BITS < 64
call_type = (flags & TCG_CALL_TYPE_MASK);
#endif
if (ret != TCG_CALL_DUMMY_ARG) {
--
1.7.5
next reply other threads:[~2011-05-03 11:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 11:03 Hans de Goede [this message]
2011-05-17 11:25 ` [Qemu-devel] [PATCH] Fix a number of unused-but-set-variable warnings (new with gcc-4.6) Christophe Fergeau
2011-05-17 17:51 ` Aurelien Jarno
2011-05-27 10:34 ` Amit Shah
2011-05-30 10:28 ` [Qemu-devel] [PATCH 0/2] Fix unused-but-set-variable warnings Christophe Fergeau
2011-05-30 10:28 ` [Qemu-devel] [PATCH 1/2] tcg: Fix unused-but-set-variable warning Christophe Fergeau
2011-05-30 10:28 ` [Qemu-devel] [PATCH 2/2] kvm: " Christophe Fergeau
2011-05-30 10:53 ` [Qemu-devel] [PATCH 0/2] Fix unused-but-set-variable warnings Amit Shah
2011-05-30 13:56 ` Christophe Fergeau
2011-05-31 5:43 ` Amit Shah
2011-05-31 7:53 ` [Qemu-devel] [PATCH-v3 " Christophe Fergeau
2011-05-31 7:53 ` [Qemu-devel] [PATCH-v3 1/2] tcg: Fix unused-but-set-variable warning Christophe Fergeau
2011-06-03 16:35 ` Aurelien Jarno
2011-05-31 7:53 ` [Qemu-devel] [PATCH-v3 2/2] kvm: " Christophe Fergeau
2011-06-10 10:43 ` Christophe Fergeau
2011-06-10 12:17 ` Stefan Hajnoczi
2011-06-10 18:46 ` Stefan Hajnoczi
2011-06-11 7:46 ` Jan Kiszka
2011-06-11 13:06 ` Stefan Hajnoczi
2011-06-14 19:50 ` Christophe Fergeau
-- strict thread matches above, loose matches on Subject: below --
2011-06-08 8:28 [Qemu-devel] [PATCH] Fix a number of unused-but-set-variable warnings (new with gcc-4.6) Hans de Goede
2011-06-08 9:22 ` Kevin Wolf
2011-06-08 11:22 ` Christophe Fergeau
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=1304420620-8409-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.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).