From: Amit Shah <amit.shah@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Static analysis using clang on the x86_64 target
Date: Wed, 13 Jan 2010 12:34:22 +0530 [thread overview]
Message-ID: <20100113070422.GE31063@amit-x200.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1001122159060.5003@linmac.oyster.ru>
On (Tue) Jan 12 2010 [22:01:15], malc wrote:
>
> Both audio.c issues are wrong, dma/sb16 is of useless operation variety
> nevertheless the "fix" is pushed, hopefuly clang shouldn't complain about
> them anymore.
Yes, the count went down to 95 from 98 after your commits.
There are a few false positives; I think clang is right in reporting
them and also that we can't really elegantly make those reports
disappear.
Amit
next prev parent reply other threads:[~2010-01-13 7:05 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 [this message]
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
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=20100113070422.GE31063@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=av1474@comtv.ru \
--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).