From: David Laight <david.laight.linux@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Ard Biesheuvel <ardb@kernel.org>, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>, Takashi Iwai <tiwai@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Uros Bizjak <ubizjak@gmail.com>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 0/4] Make gcc-8.1 and binutils-2.30 the minimum version
Date: Mon, 7 Apr 2025 19:21:10 +0100 [thread overview]
Message-ID: <20250407192110.5a7ad777@pumpkin> (raw)
In-Reply-To: <20250407164151.GB2536@sol.localdomain>
On Mon, 7 Apr 2025 09:41:51 -0700
Eric Biggers <ebiggers@kernel.org> wrote:
> On Mon, Apr 07, 2025 at 11:41:12AM +0200, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > x86 already requires gcc-8.1 since linux-6.15-rc1, which led me to
> > actually go through all version checks and make this is the minimum
> > for all architectures.
> >
> > Most of the actual resulting changes are actually for raising the
> > binutils version, which eliminates version checks on x86 and arm64.
> >
> > Arnd Bergmann (4):
> > kbuild: require gcc-8 and binutils-2.30
> > raid6: skip avx512 checks
> > x86: remove checks for binutils-2.30 and earlier
> > arm64: drop binutils version checks
>
> This is intended to supersede the patches from Uros that removed checks for
> binutils < 2.25, right? See:
>
> * https://lore.kernel.org/linux-crypto/20250404074135.520812-1-ubizjak@gmail.com/
> * https://lore.kernel.org/linux-crypto/20250404074135.520812-2-ubizjak@gmail.com
> * https://lore.kernel.org/linux-crypto/20250404074135.520812-3-ubizjak@gmail.com/
>
> If we can indeed bump up the requirement to 2.30, that would be great.
>
> Just a note though: I recently added VAES and VPCLMULQDQ instructions to
> BoringSSL, which increased the binutils requirement of building BoringSSL to
> 2.30, and this caused issues in a downstream project; e.g. see
> https://github.com/briansmith/ring/issues/2463. Specifically people complained
> about being unable to build on Amazon Linux 2 and CentOS/RHEL/Oracle Linux 7.
Just tell them RHEL 7 is no longer supported :-)
(Was a right PITA installing an extra package on a CentOS 7 system we use as
a build machine...)
In any case it is relatively easy to install a later gcc - even though it ends
up in a very obscure place.
David
>
> So I just thought I'd mention that, based on past experience with this sort of
> thing, those are the specific cases where it seems people are most likely to be
> trying to use binutils < 2.30.
>
> But if those distros are not going to be supported any longer (without
> installing newer tools on them), or even are already unsupported due to the gcc
> requirement, bumping up the binutils requirement to 2.30 sounds good to me.
>
> - Eric
>
next prev parent reply other threads:[~2025-04-07 21:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 9:41 [PATCH 0/4] Make gcc-8.1 and binutils-2.30 the minimum version Arnd Bergmann
2025-04-07 9:41 ` [PATCH 1/4] kbuild: require gcc-8 and binutils-2.30 Arnd Bergmann
2025-05-15 18:28 ` Eric Biggers
2025-05-16 8:14 ` Arnd Bergmann
2025-04-07 9:41 ` [PATCH 2/4] raid6: skip avx512 checks Arnd Bergmann
2025-04-07 9:41 ` [PATCH 3/4] x86: remove checks for binutils-2.30 and earlier Arnd Bergmann
2025-04-07 9:41 ` [PATCH 4/4] arm64: drop binutils version checks Arnd Bergmann
2025-04-08 8:46 ` Will Deacon
2025-04-08 13:10 ` Arnd Bergmann
2025-04-11 16:02 ` Will Deacon
2025-04-08 14:05 ` Mark Rutland
2025-04-07 16:41 ` [PATCH 0/4] Make gcc-8.1 and binutils-2.30 the minimum version Eric Biggers
2025-04-07 18:21 ` David Laight [this message]
2025-04-07 18:30 ` Ingo Molnar
2025-04-08 7:43 ` Arnd Bergmann
2025-04-08 8:16 ` Ingo Molnar
2025-04-08 14:20 ` Mark Rutland
2025-04-08 17:16 ` Arnd Bergmann
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250407192110.5a7ad777@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=ubizjak@gmail.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.