From: Nathan Chancellor <nathan@kernel.org>
To: Marco Elver <elver@google.com>
Cc: clang-built-linux <llvm@lists.linux.dev>,
Peter Zijlstra <peterz@infradead.org>,
Bart Van Assche <bvanassche@acm.org>,
Aaron Ballman <aaron@aaronballman.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: Clang/LLVM 'main' regression testing and -Wthread-safety
Date: Thu, 12 Feb 2026 11:57:48 -0500 [thread overview]
Message-ID: <20260212165748.GA1036664@ax162> (raw)
In-Reply-To: <CANpmjNNB_KDBXeEi6MYsPwVcDnid-8oQJvGcc6HwbOLqNBpE1Q@mail.gmail.com>
On Thu, Feb 12, 2026 at 12:53:24AM +0100, Marco Elver wrote:
> On Wed, 11 Feb 2026 at 20:40, Nathan Chancellor <nathan@kernel.org> wrote:
> > > I recall there was a CI system that did this, but lost track of what's
> > > the latest.
> >
> > Aside from our CI and Intel's, I know Linaro's toolchain group has some
> > testing of LLVM main that seems to be fairly up to date:
> >
> > https://lore.kernel.org/llvm/?q=f%3Aci_notify%40linaro.org
>
> Glad to see. I hope that if there are breakages, those are bisected
> and reported to LLVM PRs that introduced the issues?
Yes, at the very least by myself if not others since those reports are
set to the ClangBuiltLinux mailing list.
Cheers,
Nathan
prev parent reply other threads:[~2026-02-12 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aYhfK3tB0X6Y_GyV@gmail.com>
[not found] ` <177076109527.3702729.10282954256881857059.pr-tracker-bot@kernel.org>
2026-02-11 10:58 ` Clang/LLVM 'main' regression testing and -Wthread-safety Marco Elver
2026-02-11 11:54 ` Miguel Ojeda
2026-02-11 19:51 ` Nathan Chancellor
2026-02-12 12:22 ` Aaron Ballman
2026-02-12 17:01 ` Nathan Chancellor
2026-02-12 20:03 ` Miguel Ojeda
2026-02-11 19:40 ` Nathan Chancellor
2026-02-11 23:53 ` Marco Elver
2026-02-12 16:57 ` Nathan Chancellor [this message]
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=20260212165748.GA1036664@ax162 \
--to=nathan@kernel.org \
--cc=aaron@aaronballman.com \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=jemarch@gnu.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@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