From: Nathan Chancellor <nathan@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nicolas Schier <nsc@kernel.org>, Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 05/16] arch/Kconfig: Remove tautological conditions from HAS_LTO_CLANG
Date: Mon, 18 May 2026 14:36:57 -0700 [thread overview]
Message-ID: <20260518213657.GC3979157@ax162> (raw)
In-Reply-To: <6e555229-ae10-4304-ac1c-3cb02278f77f@app.fastmail.com>
On Mon, May 18, 2026 at 09:56:20AM +0200, Arnd Bergmann wrote:
> Semi-related to this: we discussed a few years ago that we may one
> day no longer need both full-lto and thin-lto.
>
> Is there still a need to keep supporting full-lto with clang-17+,
> or can we expect everyone to use the thin version thee days?
I believe there are still folks using full LTO, as I think that there is
still some performance to be gained from using full LTO over thin LTO,
but I am not sure.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-05-18 21:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 23:05 [PATCH v2 00/16] Bump minimum version of LLVM for building the kernel to 17.0.1 Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 01/16] kbuild: " Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 02/16] security/Kconfig.hardening: Remove tautological condition from CC_HAS_ZERO_CALL_USED_REGS Nathan Chancellor
2026-05-18 7:48 ` Arnd Bergmann
2026-05-18 21:05 ` Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 03/16] security/Kconfig.hardening: Remove tautological condition from FORTIFY_SOURCE Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 04/16] security/Kconfig.hardening: Remove tautological condition from CC_HAS_RANDSTRUCT Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 05/16] arch/Kconfig: Remove tautological conditions from HAS_LTO_CLANG Nathan Chancellor
2026-05-18 7:56 ` Arnd Bergmann
2026-05-18 21:36 ` Nathan Chancellor [this message]
2026-05-19 15:43 ` Sami Tolvanen
2026-05-17 23:05 ` [PATCH v2 06/16] arch/Kconfig: Remove tautological condition from AUTOFDO_CLANG Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 07/16] ARM: Drop tautological ld.lld conditions from ARCH_MULTI_V4{,T} Nathan Chancellor
2026-05-18 7:59 ` Arnd Bergmann
2026-05-17 23:05 ` [PATCH v2 08/16] riscv: Remove tautological condition from selection of ARCH_SUPPORTS_CFI Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 09/16] riscv: Drop tautological condition from TOOLCHAIN_NEEDS_OLD_ISA_SPEC Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 10/16] scripts/Makefile.warn: Drop -Wformat handling for clang < 16 Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 11/16] x86/build: Drop unnecessary '-ffreestanding' addition to KBUILD_CFLAGS Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 12/16] x86/module: Revert "Deal with GOT based stack cookie load on Clang < 17" Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 13/16] x86/entry/vdso32: Remove conditional omission of '.cfi_offset eflags' Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 14/16] kbuild: Remove check for broken scoping with clang < 17 in CC_HAS_ASM_GOTO_OUTPUT Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 15/16] compiler-clang.h: Remove __cleanup -Wunused-variable workaround Nathan Chancellor
2026-05-17 23:05 ` [PATCH v2 16/16] compiler-clang.h: Drop explicit version number from "all" diagnostic macro 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=20260518213657.GC3979157@ax162 \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=justinstitt@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nick.desaulniers+lkml@gmail.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