From: Amit Shah <amit.shah@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Static analysis using clang on the x86_64 target
Date: Thu, 14 Jan 2010 08:39:24 +0530 [thread overview]
Message-ID: <20100114030924.GF24002@amit-x200.redhat.com> (raw)
In-Reply-To: <f43fc5581001131108x69dd887cme8c242b963714558@mail.gmail.com>
On (Wed) Jan 13 2010 [19:08:11], Blue Swirl wrote:
>
> Thanks. I fixed the warnings related to Sparc32. Were there really no
> new warnings for Sparc64?
Looks like it; vl.c gets reported three times at the same locations so 3
arches have been compiled.
My test machine is down ATM, I can confirm later when it's up.
BTW for the patch
commit 884a0c7677cf8431d2a632673914994c2e01673d
pcnet: remove dead nested assignment, spotted by clang
diff --git a/hw/pcnet.c b/hw/pcnet.c
index 91d106d..44b5b31 100644
--- a/hw/pcnet.c
+++ b/hw/pcnet.c
@@ -1608,7 +1608,7 @@ static void pcnet_aprom_writeb(void *opaque,
uint32_t addr, uint32_t val)
static uint32_t pcnet_aprom_readb(void *opaque, uint32_t addr)
{
PCNetState *s = opaque;
- uint32_t val = s->prom[addr &= 15];
+ uint32_t val = s->prom[addr & 15];
#ifdef PCNET_DEBUG
printf("pcnet_aprom_readb addr=0x%08x val=0x%02x\n", addr, val);
#endif
if debugging is enabled, addr will now print a different value than
earlier.
Amit
next prev parent reply other threads:[~2010-01-14 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 18:13 [Qemu-devel] Static analysis using clang on the x86_64 target Amit Shah
2010-01-12 19:01 ` malc
2010-01-13 7:04 ` Amit Shah
2010-01-12 19:35 ` Blue Swirl
2010-01-13 7:02 ` Amit Shah
2010-01-13 19:08 ` Blue Swirl
2010-01-14 3:09 ` Amit Shah [this message]
2010-01-14 20:48 ` Blue Swirl
2010-01-21 11:41 ` Amit Shah
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=20100114030924.GF24002@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--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).