mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Marco Elver <elver@google.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH tip/locking/core v3] compiler-context-analysis: Bump required Clang version to 23
Date: Fri, 15 May 2026 08:31:58 -0700	[thread overview]
Message-ID: <1ed5f5ca-7176-4003-be14-40d2608ffeb5@acm.org> (raw)
In-Reply-To: <20260515124426.2227783-1-elver@google.com>

On 5/15/26 5:43 AM, Marco Elver wrote:
> Clang 23 introduces several major improvements:
> 
> 1. Support for multiple arguments in the `guarded_by` and
>     `pt_guarded_by` attributes [1]. This allows defining variables
>     protected by multiple context locks, where read access requires
>     holding at least one lock (shared or exclusive), and write access
>     requires holding all of them exclusively.
> 
> 2. Function pointer support [2]. We can now add attributes to function
>     pointers just like we do on normal functions.
> 
> 3. A fix to use arrays of locks [3]. Each index is now correctly treated
>     as a separate lock instance.
> 
> 4. A fix for implicit member access in attributes [4]. This allows to
>     use __guarded_by(&foo->lock) correctly.
> 
> Overall that makes it worthwhile bumping the compiler version instead of
> trying to make both Clang 22 and later work while supporting these new
> features.

Reviewed-by: Bart Van Assche <bvanassche@acm.org>

  parent reply	other threads:[~2026-05-15 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 12:43 Marco Elver
2026-05-15 12:50 ` Marco Elver
2026-05-15 15:31 ` Bart Van Assche [this message]
2026-05-20  8:28 ` [tip: locking/core] " tip-bot2 for Marco Elver
2026-05-28  9:12   ` Niklas Cassel
2026-05-28  9:37     ` Peter Zijlstra
2026-05-28 10:27       ` Peter Zijlstra
2026-05-28 10:44         ` Niklas Cassel
2026-05-28 11:15           ` Peter Zijlstra
2026-05-28 10:30 ` tip-bot2 for Marco Elver

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=1ed5f5ca-7176-4003-be14-40d2608ffeb5@acm.org \
    --to=bvanassche@acm.org \
    --cc=elver@google.com \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mingo@kernel.org \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=peterz@infradead.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®