public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: arnd@arndb.de, oleg@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: seqlock: Cure some more scoped_seqlock() optimization fails
Date: Sat, 6 Dec 2025 09:52:14 +0100	[thread overview]
Message-ID: <aTPuvn3S9tKcyYCu@gmail.com> (raw)
In-Reply-To: <20251204104332.GG2528459@noisy.programming.kicks-ass.net>

* Peter Zijlstra <peterz@infradead.org> wrote:

> Arnd reported an x86 randconfig using gcc-15 tripped over
> __scoped_seqlock_bug(). Turns out GCC chose not to inline the
> scoped_seqlock helper functions and as such was not able to optimize
> properly.

BTW., I found a Clang randconfig too that fails the build, so it's
not limited to GCC.

Thanks,

	Ingo

  parent reply	other threads:[~2025-12-06  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 10:43 seqlock: Cure some more scoped_seqlock() optimization fails Peter Zijlstra
2025-12-04 14:05 ` Arnd Bergmann
2025-12-06  8:50   ` Ingo Molnar
2025-12-06  8:52 ` Ingo Molnar [this message]
2025-12-06  8:58 ` [tip: locking/urgent] " tip-bot2 for Peter Zijlstra

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=aTPuvn3S9tKcyYCu@gmail.com \
    --to=mingo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.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