All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: llvm@lists.linux.dev, linux-kernel@vger.kernel.org, ojeda@kernel.org
Subject: Re: Prebuilt LLVM 22.1.0 uploaded
Date: Wed, 25 Feb 2026 13:12:31 -0700	[thread overview]
Message-ID: <20260225201231.GF2755225@ax162> (raw)
In-Reply-To: <CANiq72=d8c8GJEjPik5tv+LYPdFLiQOpArb1-wNck5sCzdOhkA@mail.gmail.com>

On Wed, Feb 25, 2026 at 11:55:24AM +0100, Miguel Ojeda wrote:
> On Wed, Feb 25, 2026 at 2:48 AM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > I have built and uploaded LLVM 22.1.0 to
> > https://mirrors.edge.kernel.org/pub/tools/llvm/.
> 
> As usual, thanks Nathan. I will test the new major.
> 
> Speaking of new major versions -- for the Rust "latest" combined ones,
> should they be LLVM 22 or 21? i.e. isn't the "latest" set is meant to
> match the LLVM major number? On the other hand, it probably works
> anyway, and whoever cares about LTO should use the matching. But in
> that case perhaps we should update the wording at the top of the page.

Hmmm, yeah good point. I had interpreted it as "latest LLVM version" not
"latest LLVM stable version of the corresponding major version". I guess
I had figured CONFIG_RUSTC_CLANG_LLVM_COMPATIBLE would help prevent any
problems and most users would probably prefer the latest version of each
tool, rather than the compatible ones, which are still available. I will
work on a wording update there (or just revert back to 21.1.8 for those
until Rust has LLVM 22 merged).

Cheers,
Nathan

  reply	other threads:[~2026-02-25 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  1:48 Prebuilt LLVM 22.1.0 uploaded Nathan Chancellor
2026-02-25 10:55 ` Miguel Ojeda
2026-02-25 20:12   ` Nathan Chancellor [this message]
2026-02-27 23:40     ` Miguel Ojeda

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=20260225201231.GF2755225@ax162 \
    --to=nathan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.