From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 for 2.5] QEMU does not care about left shifts of signed negative values
Date: Tue, 17 Nov 2015 20:54:22 +0100 [thread overview]
Message-ID: <564B85EE.30501@redhat.com> (raw)
In-Reply-To: <871tbobh8t.fsf@blackfin.pond.sub.org>
On 17/11/2015 19:41, Markus Armbruster wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On 17 November 2015 at 18:21, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>
>>>
>>> On 17/11/2015 19:19, Peter Maydell wrote:
>>>> That doesn't seem like more than half-good news to me. In particular,
>>>> if ubsan is still diagnosing these cases and they're still a
>>>> problem in some constant expressions
>>>
>>> Constant expressions are standardese for e.g.
>>>
>>> static int x = 1 << 31;
>>>
>>> It doesn't mean _all_ constants, and the warning only triggers with
>>> -pedantic.
>>
>> But if "-fwrapv" means "this dialect of C makes shifts of
>> negative numbers well defined and OK" then "-1 << 31"
>> should be fine and should not provoke a warning (whether in
>> a constant expression or not). If that's not what -fwrapv means,
>> then we shouldn't be using it as if it did.
>
> A warning doesn't necessarily mean "this isn't well-defined". It could
> also mean "this might not be portable", or "we think your code is ugly".
> Inferring semantics from warnings is shaky business. Instead, let's ask
> the maintainers of gcc to clarify the meaning of -fwrapv.
But again, we're not getting any warning in the first place.
Paolo
next prev parent reply other threads:[~2015-11-17 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 14:09 [Qemu-devel] [PATCH v2 for 2.5] QEMU does not care about left shifts of signed negative values Paolo Bonzini
2015-11-17 14:47 ` Laszlo Ersek
2015-11-17 15:47 ` Markus Armbruster
2015-11-17 16:54 ` Laszlo Ersek
2015-11-17 17:06 ` Paolo Bonzini
2015-11-17 18:22 ` Markus Armbruster
2015-11-17 17:39 ` Markus Armbruster
2015-11-17 17:45 ` Paolo Bonzini
2015-11-17 18:19 ` Peter Maydell
2015-11-17 18:21 ` Paolo Bonzini
2015-11-17 18:24 ` Peter Maydell
2015-11-17 18:36 ` Paolo Bonzini
2015-11-17 18:40 ` Peter Maydell
2015-11-17 18:41 ` Markus Armbruster
2015-11-17 19:54 ` Paolo Bonzini [this message]
2015-11-17 18:24 ` Markus Armbruster
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=564B85EE.30501@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=lersek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.