From: Laszlo Ersek <lersek@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for 2.5] QEMU does not care about left shifts of signed negative values
Date: Tue, 17 Nov 2015 13:17:25 +0100 [thread overview]
Message-ID: <564B1AD5.2080009@redhat.com> (raw)
In-Reply-To: <CAFEAcA-m6WmZzCh_3Ruzu=jzaNKhzTJJQWwY_E6hGyYH=orYSA@mail.gmail.com>
On 11/17/15 13:04, Peter Maydell wrote:
> On 17 November 2015 at 11:59, Markus Armbruster <armbru@redhat.com> wrote:
>> Laszlo Ersek <lersek@redhat.com> writes:
>>
>>> On 11/17/15 11:28, Paolo Bonzini wrote:
>>>>
>>>>
>>>> On 17/11/2015 11:19, Peter Maydell wrote:
>>>>> I think we should only take this patch if you can get a cast-iron
>>>>> guarantee from both clang and gcc that they will never use this
>>>>> UB to drive optimizations. As you say gcc already say this more or
>>>>> less, but clang doesn't, and if they're warning about it that to
>>>>> me suggests that they will feel freer to rely on the UB in future.
>>>>
>>>> If and when this happens we will add "-fno-strict-overflow" for clang,
>>>> just like we are using "-fno-strict-aliasing" already.
>>>
>>> How about adding "-fwrapv -fno-strict-overflow" right now? (Spelling out
>>> the latter of those explicitly for pointer arithmetic.)
>>
>> One of them, not both.
>>
>> Quote gcc manual:
>>
>> Using -fwrapv means that integer signed overflow is fully defined:
>> it wraps. When -fwrapv is used, there is no difference between
>> -fstrict-overflow and -fno-strict-overflow for integers.
>
> I thought this too, but note that it says "for integers". As Laszlo
> says, the reason to provide both is to get the -fno-strict-overflow
> behaviour for pointer arithmetic, which is not affected by -fwrapv.
Correct, that's what I meant.
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2015-11-17 12:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 9:59 [Qemu-devel] [PATCH for 2.5] QEMU does not care about left shifts of signed negative values Paolo Bonzini
2015-11-17 10:19 ` Peter Maydell
2015-11-17 10:28 ` Paolo Bonzini
2015-11-17 10:36 ` Peter Maydell
2015-11-17 10:37 ` Paolo Bonzini
2015-11-17 10:42 ` Peter Maydell
2015-11-17 10:55 ` Peter Maydell
2015-11-17 10:57 ` Paolo Bonzini
2015-11-17 11:22 ` Peter Maydell
2015-11-17 12:10 ` Paolo Bonzini
2015-11-17 12:22 ` Peter Maydell
2015-11-17 10:41 ` Laszlo Ersek
2015-11-17 10:43 ` Paolo Bonzini
2015-11-17 10:52 ` Laszlo Ersek
2015-11-17 11:59 ` Markus Armbruster
2015-11-17 12:04 ` Peter Maydell
2015-11-17 12:17 ` Laszlo Ersek [this message]
2015-11-17 13:48 ` Paolo Bonzini
2015-11-17 12:18 ` Laszlo Ersek
2015-11-17 10:26 ` Markus Armbruster
2015-11-17 10:36 ` Laszlo Ersek
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=564B1AD5.2080009@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=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).