[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191219232435.GU17708@sasha-vm>
Date: Thu, 19 Dec 2019 18:24:35 -0500
From: Sasha Levin <sashal@...nel.org>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Ard Biesheuvel <ardb@...nel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-riscv@...ts.infradead.org,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@...r.kernel.org>
Subject: Re: [PATCH AUTOSEL 5.4 316/350] int128: move __uint128_t compiler
test to Kconfig
On Wed, Dec 11, 2019 at 10:07:54AM +0000, Ard Biesheuvel wrote:
>On Tue, 10 Dec 2019 at 22:13, Sasha Levin <sashal@...nel.org> wrote:
>>
>> From: Ard Biesheuvel <ardb@...nel.org>
>>
>> [ Upstream commit c12d3362a74bf0cd9e1d488918d40607b62a3104 ]
>>
>> In order to use 128-bit integer arithmetic in C code, the architecture
>> needs to have declared support for it by setting ARCH_SUPPORTS_INT128,
>> and it requires a version of the toolchain that supports this at build
>> time. This is why all existing tests for ARCH_SUPPORTS_INT128 also test
>> whether __SIZEOF_INT128__ is defined, since this is only the case for
>> compilers that can support 128-bit integers.
>>
>> Let's fold this additional test into the Kconfig declaration of
>> ARCH_SUPPORTS_INT128 so that we can also use the symbol in Makefiles,
>> e.g., to decide whether a certain object needs to be included in the
>> first place.
>>
>> Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>
>> Signed-off-by: Ard Biesheuvel <ardb@...nel.org>
>> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>
>> Signed-off-by: Sasha Levin <sashal@...nel.org>
>
>This does not fix a bug so no need to put it in -stable
Dropped, thanks!
--
Thanks,
Sasha
Powered by blists - more mailing lists