qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Static analysis using clang on the x86_64 target
Date: Tue, 12 Jan 2010 19:35:08 +0000	[thread overview]
Message-ID: <f43fc5581001121135x790c1fb1yf3ba5883ac6bd8c3@mail.gmail.com> (raw)
In-Reply-To: <20100112181307.GD19438@amit-x200.redhat.com>

On Tue, Jan 12, 2010 at 6:13 PM, Amit Shah <amit.shah@redhat.com> wrote:
> Hello,
>
> Here's a run of the clang analyzer on qemu sources for the x86_64
> target.
>
> See
>
> http://amitshah.fedorapeople.org/clang-output/2010-01-12-9/
>
> for the results.
>
> There are a few results there which look dubious but a lot of the output
> can be useful to fix the bugs.
>
> What's nice about the tool is that the output is the source code
> annotated with the branch decisions that were taken to point out to the
> case where a bug would be triggered.
>
> Doing this for all the targets takes a really long time plus lots of
> disk space (I stopped the compile at 400M of clang output).
>
> If there's interest in this kind of result, I can post a link to the
> list every week or so. However, some bugs reported make it slightly less
> appealing as real bugs could get lost in the noise.

I'd be very interested in the results of Sparc32 and Sparc64 analyses.

  parent reply	other threads:[~2010-01-12 19:35 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 [this message]
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

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=f43fc5581001121135x790c1fb1yf3ba5883ac6bd8c3@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=amit.shah@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).