From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v2] fpu/softfloat: Silent 'bitwise negation of a boolean expression' warning
Date: Thu, 28 May 2020 08:37:34 -0500 [thread overview]
Message-ID: <1809e3cf-5750-e21e-88bf-d27f9d1fb3c3@redhat.com> (raw)
In-Reply-To: <fb5c69f1-af4c-2f6e-b47a-3b964675318a@redhat.com>
On 5/28/20 4:00 AM, Philippe Mathieu-Daudé wrote:
> On 5/28/20 10:57 AM, Thomas Huth wrote:
>> On 28/05/2020 10.48, Philippe Mathieu-Daudé wrote:
>>> When building with clang version 10.0.0-4ubuntu1, we get:
In the subject, I'd suggest s/Silent/Silence/
>>>
>>> CC lm32-softmmu/fpu/softfloat.o
>>> fpu/softfloat.c:3365:13: error: bitwise negation of a boolean expression; did you mean logical negation? [-Werror,-Wbool-operation]
>>> absZ &= ~ ( ( ( roundBits ^ 0x40 ) == 0 ) & roundNearestEven );
>>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> fpu/softfloat.c:3423:18: error: bitwise negation of a boolean expression; did you mean logical negation? [-Werror,-Wbool-operation]
>>> absZ0 &= ~ ( ( (uint64_t) ( absZ1<<1 ) == 0 ) & roundNearestEven );
>>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
Also, do you need to list all errors, or will just one or two
representative errors be sufficient?
>>>
>>> Fix by rewriting the fishy bitwise AND of two bools as an int.
>>>
>>> Suggested-by: Eric Blake <eblake@redhat.com>
>>> Buglink: https://bugs.launchpad.net/bugs/1881004
>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>> ---
>>> +++ b/fpu/softfloat.c
>>> @@ -3362,7 +3362,9 @@ static int32_t roundAndPackInt32(bool zSign, uint64_t absZ,
>>> }
>>> roundBits = absZ & 0x7F;
>>> absZ = ( absZ + roundIncrement )>>7;
>>> - absZ &= ~ ( ( ( roundBits ^ 0x40 ) == 0 ) & roundNearestEven );
>>> + if (((roundBits ^ 0x40) == 0) && roundNearestEven) {
>>> + absZ &= ~1;
>>> + }
>>
>> You could get rid of some more parentheses now:
>>
>> if ((roundBits ^ 0x40) == 0 && roundNearestEven)
>>
>> ... also in the other hunks.
>
> I first wrote
>
> if (!(roundBits ^ 0x40) && roundNearestEven)
>
> But then thought this would diverge from Eric suggestion, so I kept what
> he wrote (which is a bit closer to the style of rest of this file).
I don't mind the patch as-is for minimizing churn and matching existing
style, but I also would not be opposed if you wanted to elide
unnecessary ().
>
>>
>> Anyway:
>> Reviewed-by: Thomas Huth <thuth@redhat.com>
>>
>
> Thanks!
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-05-28 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:48 [PATCH v2] fpu/softfloat: Silent 'bitwise negation of a boolean expression' warning Philippe Mathieu-Daudé
2020-05-28 8:57 ` Thomas Huth
2020-05-28 9:00 ` Philippe Mathieu-Daudé
2020-05-28 13:37 ` Eric Blake [this message]
2020-05-28 13:41 ` Philippe Mathieu-Daudé
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=1809e3cf-5750-e21e-88bf-d27f9d1fb3c3@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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).