[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <409e13bc-9e0c-9db6-977b-1a90b18d278e@gentoo.org>
Date: Mon, 27 Jun 2016 19:41:49 +0200
From: Luca Barbato <lu_zero@...too.org>
To: musl@...ts.openwall.com
Subject: Re: Fix warnings when build with clang
On 27/06/16 19:21, Rich Felker wrote:
> On Mon, Jun 27, 2016 at 10:01:52AM -0700, weimingz@...eaurora.org wrote:
>> On 2016-06-25 02:37, Szabolcs Nagy wrote:
>>> * Zhao, Weiming <weimingz@...eaurora.org> [2016-06-24 17:18:23 -0700]:
>>>> Clang gives warnings about the missing parentheses for bitwise ops.
>>>>
>>>> It's not functional but just code readability.
>>>>
>>>> musl-m3/include/endian.h:32:25: warning: '&' within '|'
>>>> [-Wbitwise-op-parentheses]
>>>> return __x>>24 | __x>>8&0xff00 | __x<<8&0xff0000 | __x<<24;
>>>> ~ ~~~~~~^~~~~~~
>>>
>>> if clang warns about system headers that's a clang bug.
>>
>> The endian.h is a musl file.
>
> Right, which is why it's a system header.
I'm not sure there is a simple way to know what's a system header and
what is not, beside keeping a list.
And even in that case I'm not so sure the compiler should hide warnings
(no matter how fringe this actual warning is).
lu
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
