mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: [PATCH 0/4] scripts/Kconfig.toolchain: Document minimum supported versions for dynamic checks
Date: Tue, 10 Nov 2026 23:42:39 -0600	[thread overview]
Message-ID: <20261110-kconfig-toolchain-updates-v1-0-6d4fb636290e@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. The first cleans up CONFIG_CC_HAS_NO_PROFILE_FN_ATTR since it
is always 'y'. The second cleans up '-fno-addrsig' handling, as this is
an always supported clang option for a clang specific feature. The third
unifies the GCC specific "no allow store data races" flag.

I tried to add some commentary when the option was unsupported by a
particular implementation but I am on the fence about whether that is
actually useful or not, especially since they might go stale if the
other implementation starts supporting them. However, I included it
anyways since compiler_attributes.h can have the same problem and folks
can check before removing or adjusting the option. If people don't like
it, I am fine with dropping them and only documenting the supported
versions.

---
Nathan Chancellor (4):
      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
      scripts/Kconfig.toolchain: Document minimum supported versions for dynamic checks

 Makefile                  |  5 -----
 kernel/gcov/Kconfig       |  1 -
 scripts/Kconfig.toolchain | 45 ++++++++++++++++++++++++++++++++++++---------
 3 files changed, 36 insertions(+), 15 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


             reply	other threads:[~2026-11-11  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  5:42 Nathan Chancellor [this message]
2026-11-11  5:42 ` [PATCH 1/4] scripts/Kconfig.toolchain: Remove CONFIG_CC_HAS_NO_PROFILE_FN_ATTR Nathan Chancellor
2026-11-11  5:42 ` [PATCH 2/4] scripts/Kconfig.toolchain: Do not dynamically probe '-fno-addrsig' Nathan Chancellor
2026-11-11  5:42 ` [PATCH 3/4] scripts/Kconfig.toolchain: Clean up '-fno-allow-store-data-races' handling Nathan Chancellor
2026-11-11  5:42 ` [PATCH 4/4] 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=20261110-kconfig-toolchain-updates-v1-0-6d4fb636290e@kernel.org \
    --to=nathan@kernel.org \
    --cc=arnd@arndb.de \
    --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=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=ndesaulniers@google.com \
    --cc=nsc@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®