public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Marco Elver <elver@google.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	pkg-llvm-team@lists.alioth.debian.org
Subject: Re: [PATCH] lib/Kconfig.debug: Require a release version of LLVM 22 for context analysis
Date: Wed, 25 Feb 2026 15:52:28 +0100	[thread overview]
Message-ID: <20260225145228.GB1282955@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260224-bump-clang-ver-context-analysis-v1-1-16cc7a90a040@kernel.org>

On Tue, Feb 24, 2026 at 04:16:30PM -0700, Nathan Chancellor wrote:
> Using a prerelease version as a minimum supported version for
> CONFIG_WARN_CONTEXT_ANALYSIS was reasonable to do while LLVM 22 was the
> development version so that people could immediately build from main and
> start testing and validating this in their own code. However, it can be
> problematic when using prerelease versions of LLVM 22, such as Android
> clang 22.0.1 (the current android mainline compiler) or when bisecting
> LLVM between llvmorg-22-init and llvmorg-23-init, to build the kernel,
> as all compiler fixes for the context analysis may not be present,
> potentially resulting in warnings that can easily turn into errors.
> 
> Now that LLVM 22 is released as 22.1.0, upgrade the check to require at
> least this version to ensure that a user's toolchain actually has all
> the changes needed for a smooth experience with context analysis.
> 
> Fixes: 3269701cb256 ("compiler-context-analysis: Add infrastructure for Context Analysis with Clang")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
> Peter, could you take this for a 7.0-rc?

Yes, I can. I would however appreciate the Debian folks to quickly push
an update to the clang-22/experimental package. Otherwise I can't run
this fancy stuff myself no moar.

  parent reply	other threads:[~2026-02-25 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 23:16 [PATCH] lib/Kconfig.debug: Require a release version of LLVM 22 for context analysis Nathan Chancellor
2026-02-25  7:00 ` Marco Elver
2026-02-25 14:52 ` Peter Zijlstra [this message]
2026-02-25 18:53   ` Nathan Chancellor
2026-02-25 22:23     ` Peter Zijlstra
2026-02-26  8:08       ` Sylvestre Ledru
2026-02-25 15:31 ` [tip: locking/urgent] " tip-bot2 for 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=20260225145228.GB1282955@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bvanassche@acm.org \
    --cc=elver@google.com \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=pkg-llvm-team@lists.alioth.debian.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