From: Paolo Bonzini <pbonzini@redhat.com>
To: Steven Noonan <steven@uplinklabs.net>,
Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] disas/arm: avoid clang shifting negative signed warning
Date: Tue, 10 Nov 2015 21:18:18 +0100 [thread overview]
Message-ID: <5642510A.3070608@redhat.com> (raw)
In-Reply-To: <CAKbGBLiF5tYNk_GA4XWPTvQuvux5khyVazkFi+REetuo1Th0dg@mail.gmail.com>
On 10/11/2015 20:51, Steven Noonan wrote:
> I don't read this warning as "clang will do crazy things with your
> code eventually". Clang has always been very verbose when it comes to
> undefined behavior, and I don't think that's really a bad thing to do.
Sure, but it doesn't belong in -Wall. It's what -Wextra is for.
Paolo
next prev parent reply other threads:[~2015-11-10 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 15:57 [Qemu-devel] [PATCH 0/3] fix clang negative signed bit shift warning Stefan Hajnoczi
2015-11-10 15:57 ` [Qemu-devel] [PATCH 1/3] monitor: avoid clang shifting negative signed warning Stefan Hajnoczi
2015-11-13 15:37 ` Eduardo Habkost
2015-11-10 15:57 ` [Qemu-devel] [PATCH 2/3] tpm: " Stefan Hajnoczi
2015-11-10 15:57 ` [Qemu-devel] [PATCH 3/3] disas/arm: " Stefan Hajnoczi
2015-11-10 17:33 ` Paolo Bonzini
2015-11-10 17:48 ` Peter Maydell
2015-11-10 17:59 ` Paolo Bonzini
2015-11-10 18:52 ` Markus Armbruster
2015-11-10 19:51 ` Steven Noonan
2015-11-10 20:06 ` Markus Armbruster
2015-11-10 20:17 ` Steven Noonan
2015-11-10 20:18 ` Paolo Bonzini [this message]
2015-11-10 16:04 ` [Qemu-devel] [PATCH 0/3] fix clang negative signed bit shift warning Peter Maydell
2015-11-16 14:23 ` Peter Maydell
2015-11-16 15:20 ` Peter Maydell
2015-11-17 3:50 ` Stefan Hajnoczi
2015-11-17 3:53 ` 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=5642510A.3070608@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=steven@uplinklabs.net \
/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).