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, 21 Jan 2010 17:11:20 +0530 [thread overview]
Message-ID: <20100121114120.GE25684@amit-x200.redhat.com> (raw)
In-Reply-To: <20100113070254.GD31063@amit-x200.redhat.com>
On (Wed) Jan 13 2010 [12:32:54], Amit Shah wrote:
> >
> > I'd be very interested in the results of Sparc32 and Sparc64 analyses.
>
> OK, I added the two targets to the run and got the following result:
>
> http://amitshah.fedorapeople.org/clang-output/2010-01-13-1/
>
> The bug count went up from 95 for just x86-64 to 131.
The count currently is at 107:
http://amitshah.fedorapeople.org/clang-output/2010-01-21-1/
A few new ones have been introduced.
Amit
prev parent reply other threads:[~2010-01-21 11:42 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
2010-01-14 20:48 ` Blue Swirl
2010-01-21 11:41 ` Amit Shah [this message]
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=20100121114120.GE25684@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).