[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5A790652-1B22-4D13-AAC5-5D9931E90903@zytor.com>
Date: Fri, 07 Mar 2025 11:30:35 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>
CC: Laurent.pinchart@...asonboard.com, airlied@...il.com,
akpm@...ux-foundation.org, alistair@...ple.id.au,
andrew+netdev@...n.ch, andrzej.hajda@...el.com,
arend.vanspriel@...adcom.com, awalls@...metrocast.net, bp@...en8.de,
bpf@...r.kernel.org, brcm80211-dev-list.pdl@...adcom.com,
brcm80211@...ts.linux.dev, dave.hansen@...ux.intel.com,
davem@...emloft.net, dmitry.torokhov@...il.com,
dri-devel@...ts.freedesktop.org, eajames@...ux.ibm.com,
edumazet@...gle.com, eleanor15x@...il.com, gregkh@...uxfoundation.org,
hverkuil@...all.nl, jernej.skrabec@...il.com, jirislaby@...nel.org,
jk@...abs.org, joel@....id.au, johannes@...solutions.net,
jonas@...boo.se, jserv@...s.ncku.edu.tw, kuba@...nel.org,
linux-fsi@...ts.ozlabs.org, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
linux-mtd@...ts.infradead.org, linux-serial@...r.kernel.org,
linux-wireless@...r.kernel.org, linux@...musvillemoes.dk,
louis.peens@...igine.com, maarten.lankhorst@...ux.intel.com,
mchehab@...nel.org, mingo@...hat.com, miquel.raynal@...tlin.com,
mripard@...nel.org, neil.armstrong@...aro.org, netdev@...r.kernel.org,
oss-drivers@...igine.com, pabeni@...hat.com,
parthiban.veerasooran@...rochip.com, rfoss@...nel.org, richard@....at,
simona@...ll.ch, tglx@...utronix.de, tzimmermann@...e.de,
vigneshr@...com, visitorckw@...il.com, x86@...nel.org,
yury.norov@...il.com
Subject: Re: [PATCH v3 00/16] Introduce and use generic parity16/32/64 helper
On March 7, 2025 10:49:56 AM PST, Andrew Cooper <andrew.cooper3@...rix.com> wrote:
>> (int)true most definitely is guaranteed to be 1.
>
>That's not technically correct any more.
>
>GCC has introduced hardened bools that intentionally have bit patterns
>other than 0 and 1.
>
>https://gcc.gnu.org/gcc-14/changes.html
>
>~Andrew
Bit patterns in memory maybe (not that I can see the Linux kernel using them) but for compiler-generated conversations that's still a given, or the manager isn't C or anything even remotely like it.
Powered by blists - more mailing lists