From: Yunseong Kim <yunseong.kim@est.tech>
To: aaron.ballman@intel.com, Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Nicolas Schier <nsc@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittoteggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <kprateek.nayak@amd.com>
Cc: llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, thakis@chromium.org
Subject: v7.4-rc2 kernel build failure when using the upstream LLVM 24 with -Wunsequenced-volatile
Date: Thu, 19 Nov 2026 14:23:51 +0100 [thread overview]
Message-ID: <624efab4-f1e3-4bd1-8ddc-60bba4b5d798@est.tech> (raw)
Hi,
After https://github.com/llvm/llvm-project/pull/180955 feature
"[clang] Add check in SemaChecking for multiple unsequenced volatile accesses",
v7.4-rc2 kernel compiling with the upstream LLVM 24 was failed.
kernel/sched/build_utility.c:86:
kernel/sched/topology.c:2008:29: error: unsequenced accesses to volatile qualified 'jiffies' [-Werror,-Wunsequenced-volatile]
1998 | .last_balance = jiffies,
| ~~~~~~~
1999 | .balance_interval = sd_weight,
2000 |
2001 | /* 50% success rate */
2002 | .newidle_call = 512,
2003 | .newidle_success = 256,
2004 | .newidle_ratio = 512,
2005 | .newidle_stamp = now,
2006 |
2007 | .max_newidle_lb_cost = 0,
2008 | .last_decay_max_lb_cost = jiffies,
| ^
1 error generated.
Is that mean topology code have a potential issue, or is this a compiler's
false positive? The same error message can be reproduced on the example
user space program.
$ cat jiffies.c
extern volatile unsigned long jiffies;
struct sample {
unsigned long a;
unsigned long b;
};
void init(struct sample *p)
{
*p = (struct sample) {
.a = jiffies,
.b = jiffies,
};
}
$ clang --version --verbose
clang version 24.0.0git (https://github.com/yskzalloc/llvm-project.git 5d20c85f4e1b8755b655bf1782b094fb35ec48d1)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /home/debian-sid/kcov-dataflow/llvm-project/build-upstream-check/bin
$ clang -std=gnu11 -Werror=unsequenced-volatile -fsyntax-only jiffies.c
jiffies.c:12:14: error: unsequenced accesses to volatile qualified 'jiffies' [-Werror,-Wunsequenced-volatile]
11 | .a = jiffies,
| ~~~~~~~
12 | .b = jiffies,
| ^
1 error generated.
Thanks!
Best regards,
Yunseong
next reply other threads:[~2026-11-19 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 13:23 Yunseong Kim [this message]
2026-11-19 14:13 ` Yunseong Kim
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=624efab4-f1e3-4bd1-8ddc-60bba4b5d798@est.tech \
--to=yunseong.kim@est.tech \
--cc=aaron.ballman@intel.com \
--cc=bsegall@google.com \
--cc=juri.lelli@redhat.com \
--cc=justinstitt@google.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nsc@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=thakis@chromium.org \
--cc=vincent.guittoteggemann@arm.com \
/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®