From: Nathan Chancellor <nathan@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
D Scott Phillips <scott@os.amperecomputing.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Revisiting c0a454b9044f
Date: Mon, 14 Jul 2025 12:52:05 -0700 [thread overview]
Message-ID: <20250714195205.GA3723043@ax162> (raw)
Hi all,
I am looking to potentially bump the minimum version of LLVM for
building the kernel to 15.0.0 after the next merge window. In my quest
to look for workarounds that can be dropped, I noticed that
CONFIG_ARM64_BTI_KERNEL was disabled unconditionally for GCC in commit
c0a454b9044f ("arm64/bti: Disable in kernel BTI when cross section
thunks are broken") as a result of [1]. Looking at that GCC report, it
seems like the AArch64 ABI now documents [2] the GNU toolchain's
behavior as expected and LLVM has been adjusted [3][4][5] to match. Do I
need to block CONFIG_ARM64_BTI_KERNEL from being selected with LLVM
21.0.0? Or should the kernel adjust its expectations now that the ABI
and toolchains all agree?
Cheers,
Nathan
[1]: https://gcc.gnu.org/pr106671
[2]: https://github.com/ARM-software/abi-aa/commit/606ce44fe4d3419c15cd9ed598f18fb5d520fcfc
[3]: https://github.com/llvm/llvm-project/commit/7af2b51e761f49974a64c3009882239cea618f2a
[4]: https://github.com/llvm/llvm-project/commit/edf21314c98a4fe05d48f83dfab2b201ed8bfe9c
[5]: https://github.com/llvm/llvm-project/commit/098b0d18add97dea94e16006486b2fded65e228d
next reply other threads:[~2025-07-14 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 19:52 Nathan Chancellor [this message]
2025-07-15 11:16 ` Revisiting c0a454b9044f Mark Rutland
2025-07-16 18:26 ` Nathan Chancellor
2025-07-17 13:47 ` Mark Rutland
2025-12-30 15:06 ` ARM64_BTI_KERNEL and gcc? (was Re: Revisiting c0a454b9044f ) Mikko Rapeli
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=20250714195205.GA3723043@ax162 \
--to=nathan@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=scott@os.amperecomputing.com \
--cc=will@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