From: Stefan Weil <sw@weilnetz.de>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] clang warnings too noisy
Date: Sat, 07 Mar 2015 10:04:57 +0100 [thread overview]
Message-ID: <54FABF39.4020404@weilnetz.de> (raw)
In-Reply-To: <CAJSP0QWdGTKYMLcyTWjUfAYA2R964T-ESkBpnVn4F-yVx2Nv6w@mail.gmail.com>
Am 06.03.2015 um 20:06 schrieb Stefan Hajnoczi:
> Hi Peter,
> You are rejecting pull requests that produce warnings under clang.
>
> clang 3.5.0 on Fedora 21 produces so much noise that it's extremely
> tedious and error-prone to try finding relevant new warnings.
>
> Are you using a different clang version which produces fewer warnings?
>
> Is anyone working on making QEMU build cleanly under clang? Under gcc
> people regularly submit patches to keep the build clean (e.g. recent
> gcc 5 fixes).
>
> Currently I'm not happy wrangling with clang when very few people seem
> to use it or care enough to make QEMU build cleanly.
>
Compilation with different compilers is still very important to detect
hidden bugs. Here is the latest example which I found because of your
e-mail:
block/iscsi.c:1329:20: warning: comparison of array 'iscsi_url->user'
not equal to a null pointer is always true [-Wtautological-pointer-compare]
The code is wrong (I'll send a patch), and the code where it was copied
from is wrong, too (see https://github.com/sahlberg/libiscsi/pull/146).
I use clang on Mac from time to time and used it some time ago on Linux.
Regards
Stefan
next prev parent reply other threads:[~2015-03-07 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 19:06 [Qemu-devel] clang warnings too noisy Stefan Hajnoczi
2015-03-06 23:47 ` Peter Maydell
2015-03-07 11:14 ` Paolo Bonzini
2015-03-07 11:29 ` Stefan Weil
2015-03-10 10:35 ` Stefan Hajnoczi
2015-03-07 9:04 ` Stefan Weil [this message]
2015-03-07 9:50 ` Stefan Weil
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=54FABF39.4020404@weilnetz.de \
--to=sw@weilnetz.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).