From: Nathan Chancellor <nathan@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>, Nicolas Schier <nsc@kernel.org>
Cc: Julian Braha <julianbraha@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Arnd Bergmann <arnd@arndb.de>, Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
llvm@lists.linux.dev,
Charlie Jenkins <thecharlesjenkins@gmail.com>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
linux-riscv@lists.infradead.org,
Linus Torvalds <torvalds@linuxfoundation.org>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH v2 0/6] scripts/Kconfig.toolchain: Document minimum supported versions for dynamic checks
Date: Wed, 11 Nov 2026 17:52:02 -0700 [thread overview]
Message-ID: <20261111-kconfig-toolchain-updates-v2-0-b2d9415c1757@kernel.org> (raw)
Hi all,
Now that we have a fairly unified location for compiler and linker
feature checks in scripts/Kconfig.toolchain, we should make it easy to
clean up the checks as they become obsolete through minimum supported
version bumps by documenting when they were first supported. I somewhat
modeled this after the documentation in compiler_attributes.h but I did
not want it to be as verbose.
In doing this archaeology, I developed a few prerequisite clean up
patches, mostly around removing code that is practically dead through
minimum versions or adjusting options that are only supported in one
compiler. See the individual patches for the details.
---
Changes in v2:
- Fix versions for a few entries (Julian)
- Add patch fixing check for asm goto with tied outputs in riscv code
- Add patch eliminating check for asm goto with tied outputs, as all
compilers that properly support asm goto with outputs will have
support for tied outputs
- Add links to tools where feature is supported/changed to make future
auditing easier
- Adjust comment format to be a little more succinct
- Reword commit messages accordingly
- Link to v1: https://patch.msgid.link/20261110-kconfig-toolchain-updates-v1-0-6d4fb636290e@kernel.org
---
Nathan Chancellor (6):
scripts/Kconfig.toolchain: Remove CONFIG_CC_HAS_NO_PROFILE_FN_ATTR
scripts/Kconfig.toolchain: Do not dynamically probe '-fno-addrsig'
scripts/Kconfig.toolchain: Clean up '-fno-allow-store-data-races' handling
riscv: checksum: Fix CC_HAS_ASM_GOTO_TIED_OUTPUT check
Eliminate CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT
scripts/Kconfig.toolchain: Document minimum supported versions for dynamic checks
Makefile | 5 ---
arch/riscv/lib/csum.c | 4 +--
arch/x86/include/asm/uaccess.h | 82 ++++++++++++++++++++----------------------
kernel/gcov/Kconfig | 1 -
scripts/Kconfig.toolchain | 80 +++++++++++++++++++++++++++++++++--------
5 files changed, 107 insertions(+), 65 deletions(-)
---
base-commit: 7f705c0ad1c7cab3d8de99a3a67937bc82fc8481
base-tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
change-id: 20261110-kconfig-toolchain-updates-d8b351370a5f
Best regards,
--
Cheers,
Nathan
next reply other threads:[~2026-11-12 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 0:52 Nathan Chancellor [this message]
2026-11-12 0:52 ` [PATCH v2 1/6] scripts/Kconfig.toolchain: Remove CONFIG_CC_HAS_NO_PROFILE_FN_ATTR Nathan Chancellor
2026-11-12 0:52 ` [PATCH v2 2/6] scripts/Kconfig.toolchain: Do not dynamically probe '-fno-addrsig' Nathan Chancellor
2026-11-12 0:52 ` [PATCH v2 3/6] scripts/Kconfig.toolchain: Clean up '-fno-allow-store-data-races' handling Nathan Chancellor
2026-11-12 0:52 ` [PATCH v2 4/6] riscv: checksum: Fix CC_HAS_ASM_GOTO_TIED_OUTPUT check Nathan Chancellor
2026-11-12 0:52 ` [PATCH v2 5/6] Eliminate CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT Nathan Chancellor
2026-11-12 0:52 ` [PATCH v2 6/6] scripts/Kconfig.toolchain: Document minimum supported versions for dynamic checks Nathan Chancellor
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=20261111-kconfig-toolchain-updates-v2-0-b2d9415c1757@kernel.org \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=julianbraha@gmail.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=nsc@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tglx@kernel.org \
--cc=thecharlesjenkins@gmail.com \
--cc=torvalds@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®