From: David Gibson <david@gibson.dropbear.id.au>
To: Eli <793317@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 793317] [NEW] Large amount of write-only variables
Date: Mon, 6 Jun 2011 16:06:19 +1000 [thread overview]
Message-ID: <20110606060619.GB1833@yookeroo.fritz.box> (raw)
In-Reply-To: <20110606010233.7730.48177.malonedeb@chaenomeles.canonical.com>
On Mon, Jun 06, 2011 at 01:02:33AM -0000, Eli wrote:
> Public bug reported:
>
> Whenever I try to compile the source from the git repo, it gets a large
> number of "set but not used" errors, in files such as:
>
> hw/usb_ochi.c (line 526, 1114, and 1108)
> hw/lsi53c895a.c (line 892)
> kvm.c (line 973)
> target-alpha/translate.c (line 1472, 1470)
> linux-user/syscall.c (line 7062, 3754)
> exec.c (line 1211)
> linux-user/linuxload.c (line 60)
>
> Really now, why would anyone create so many write-only variables knowing
> that it's compiled with write-only variables causing errors..?
It's a new warning in gcc 4.6, which is why these weren't found
before.
--
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-06-06 6:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 1:02 [Qemu-devel] [Bug 793317] [NEW] Large amount of write-only variables Eli
2011-06-06 2:08 ` [Qemu-devel] [Bug 793317] " Brad Hards
2011-06-06 2:23 ` Eli
2011-06-06 2:42 ` Brad Hards
2011-06-06 2:55 ` Eli
2011-06-06 3:06 ` Brad Hards
2011-06-06 3:19 ` Eli
2011-06-06 6:06 ` David Gibson [this message]
2011-06-06 8:29 ` [Qemu-devel] [Bug 793317] [NEW] " agraf
2011-06-06 10:15 ` [Qemu-devel] [Bug 793317] " Christophe Fergeau
2011-12-24 23:04 ` Peter Maydell
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=20110606060619.GB1833@yookeroo.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=793317@bugs.launchpad.net \
--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).