qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU versus Facebook's Infer static analysis tool
Date: Mon, 16 Nov 2015 10:41:50 +0100	[thread overview]
Message-ID: <5649A4DE.4020605@redhat.com> (raw)
In-Reply-To: <CAFEAcA9rYRBTGK=TUhx9n1K0rVP1sfGf52CNQS3uD48mftqVTQ@mail.gmail.com>



On 14/11/2015 22:53, Peter Maydell wrote:
> That's a shame, because it would have been nice to include another
> kind of static analysis in what we run on QEMU (especially since
> the coverity tests are "only runs every so often when we do a build"),
> and the ability to do incremental analysis would have meant you could
> include it in day to day workflow much more easily.
> 
> In summary: worth keeping an eye on to see if it improves, but for
> now I figured I'd just post this email to the list to save anybody
> else running through the same process to come to the same conclusion.

Great, thanks!

Blue Swirl ran clang static analyzer back in the day.  Now that we've
fixed a lot of Coverity issues it's probably time to rerun it again and
see whether free static analyzers can help us as much as Coverity does.

However, we still have a few hundred flagged false positives in
Coverity, so we can expect that any static analyzer will have a hard
time finding real issues in the code.

Paolo

  reply	other threads:[~2015-11-16  9:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14 21:53 [Qemu-devel] QEMU versus Facebook's Infer static analysis tool Peter Maydell
2015-11-16  9:41 ` Paolo Bonzini [this message]
2015-11-25  7:40 ` Stefan Hajnoczi

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=5649A4DE.4020605@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).