[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=wg0r4XutgSRxzeEi6QQUJ4oej5o-kdS8j02KrLEXT4WnA@mail.gmail.com>
Date: Mon, 18 Nov 2024 09:09:55 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Vincent Mailhol <mailhol.vincent@...adoo.fr>
Cc: David Laight <David.Laight@...lab.com>, Yury Norov <yury.norov@...il.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>, Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-sparse@...r.kernel.org" <linux-sparse@...r.kernel.org>,
Rikard Falkeborn <rikard.falkeborn@...il.com>
Subject: Re: [PATCH v4 1/2] compiler.h: add const_true()
On Sun, 17 Nov 2024 at 19:22, Vincent Mailhol
<mailhol.vincent@...adoo.fr> wrote:
>
> I did a tree wide replacement of __is_constexpr() with is_const() and
> did an allyesconfig build test. It yields a -Wint-in-bool-context
> warning in GCC for both the "0*!(x)" and the "0&&(x)" each time the
> expression contains non-boolean operators, for example: * or <<.
Grr. Annoying. But yeah, replace the "!" with "!= 0" and I guess it
should be ok.
Linus
Powered by blists - more mailing lists