From: Nathan Chancellor <nathan@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Jordan Abrahams-Whitehead <ajordanr@google.com>,
Nicolas Schier <nsc@kernel.org>,
Julian Braha <julianbraha@gmail.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: Re: [PATCH 2/4] scripts/Kconfig.toolchain: Do not dynamically probe '-fno-addrsig'
Date: Wed, 11 Nov 2026 11:36:11 -0700 [thread overview]
Message-ID: <20261111183611.GB1452558@ax162> (raw)
In-Reply-To: <CAKwvOdnFG1ACEvGPXGW1XK_3QN+5UaR_9EumhmrsyKOs0aYCPQ@mail.gmail.com>
On Wed, Nov 11, 2026 at 08:51:05AM -0800, Nick Desaulniers wrote:
> Jordan, I know you were playing with -Wl,--icf=all recently. Looks
> like the kernel does not use it; AFAIK, no one has ever tried. Even
> -Wl,--icf=safe. Worth a shot to see if it boots. If we did, we'd
> have to update this kconfig check (the linker flag is only supported
> by LLD). Even if the result doesn't boot, it's perhaps worth doing
> builds with BOTH to see what kind of savings are possible at the
> limit.
FWIW, ICF came up once before through OpenMandriva defaulting it on in
their toolchain.
https://github.com/ClangBuiltLinux/linux/issues/1341
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-11-11 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 5:42 [PATCH 0/4] scripts/Kconfig.toolchain: Document minimum supported versions for dynamic checks Nathan Chancellor
2026-11-11 5:42 ` [PATCH 1/4] scripts/Kconfig.toolchain: Remove CONFIG_CC_HAS_NO_PROFILE_FN_ATTR Nathan Chancellor
2026-11-11 19:06 ` Nick Desaulniers
2026-11-11 19:10 ` Nathan Chancellor
2026-11-11 19:29 ` Nick Desaulniers
2026-11-11 5:42 ` [PATCH 2/4] scripts/Kconfig.toolchain: Do not dynamically probe '-fno-addrsig' Nathan Chancellor
2026-11-11 16:51 ` Nick Desaulniers
2026-11-11 18:36 ` Nathan Chancellor [this message]
2026-11-11 18:45 ` Nick Desaulniers
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
2026-11-11 19:01 ` Julian Braha
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=20261111183611.GB1452558@ax162 \
--to=nathan@kernel.org \
--cc=ajordanr@google.com \
--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®