archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <>
To: Ard Biesheuvel <>
Cc: Herbert Xu <>,
	Linux Kernel Mailing List <>,
	stable <>,
	Masahiro Yamada <>,
	<>,, Ard Biesheuvel <>,
	linux-arm-kernel <>
Subject: Re: [PATCH AUTOSEL 5.4 316/350] int128: move __uint128_t compiler test to Kconfig
Date: Thu, 19 Dec 2019 18:24:35 -0500	[thread overview]
Message-ID: <20191219232435.GU17708@sasha-vm> (raw)
In-Reply-To: <>

On Wed, Dec 11, 2019 at 10:07:54AM +0000, Ard Biesheuvel wrote:
>On Tue, 10 Dec 2019 at 22:13, Sasha Levin <> wrote:
>> From: Ard Biesheuvel <>
>> [ 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 <>
>> Signed-off-by: Ard Biesheuvel <>
>> Signed-off-by: Herbert Xu <>
>> Signed-off-by: Sasha Levin <>
>This does not fix a bug so no need to put it in -stable

Dropped, thanks!


      reply	other threads:[~2019-12-19 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-12-10 21:05 ` [PATCH AUTOSEL 5.4 196/350] spi: sifive: disable clk when probe fails and remove Sasha Levin
2019-12-10 21:07 ` [PATCH AUTOSEL 5.4 316/350] int128: move __uint128_t compiler test to Kconfig Sasha Levin
2019-12-11 10:07   ` Ard Biesheuvel
2019-12-19 23:24     ` Sasha Levin [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191219232435.GU17708@sasha-vm \ \ \ \ \ \ \ \ \ \ \

* 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).