From: David Gibson <david@gibson.dropbear.id.au>
To: Alexander Graf <agraf@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] ppc: remove a write-only variable
Date: Mon, 11 Apr 2011 14:30:28 +1000 [thread overview]
Message-ID: <20110411043028.GN3151@yookeroo> (raw)
In-Reply-To: <B67107F9-BA40-436F-9659-72B91FDAA62A@suse.de>
On Sat, Apr 09, 2011 at 05:28:06PM +0200, Alexander Graf wrote:
>
>
>
>
> Am 09.04.2011 um 16:56 schrieb Blue Swirl <blauwirbel@gmail.com>:
>
> > Remove a write-only variable, spotted by GCC 4.6.0:
> > /src/qemu/hw/ppc.c: In function 'power7_set_irq':
> > /src/qemu/hw/ppc.c:255:9: error: variable 'cur_level' set but not used
> > [-Werror=unused-but-set-variable]
> >
> > Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> > ---
> > hw/ppc.c | 2 --
> > 1 files changed, 0 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/ppc.c b/hw/ppc.c
> > index dabb816..1873328 100644
> > --- a/hw/ppc.c
> > +++ b/hw/ppc.c
> > @@ -252,11 +252,9 @@ void ppc970_irq_init (CPUState *env)
> > static void power7_set_irq (void *opaque, int pin, int level)
> > {
> > CPUState *env = opaque;
> > - int cur_level;
> >
> > LOG_IRQ("%s: env %p pin %d level %d\n", __func__,
> > env, pin, level);
> > - cur_level = (env->irq_input_state >> pin) & 1;
>
> David, Ben?
That should be fine. It's a hang over from the ppc970 code which I
adapted.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2011-04-11 4:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 14:56 [Qemu-devel] [PATCH] ppc: remove a write-only variable Blue Swirl
2011-04-09 15:28 ` [Qemu-devel] " Alexander Graf
2011-04-11 4:30 ` David Gibson [this message]
2011-04-11 7:48 ` Alexander Graf
2011-04-11 17:25 ` [Qemu-devel] " Blue Swirl
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=20110411043028.GN3151@yookeroo \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=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).