From: Nathan Chancellor <nathan@kernel.org>
To: llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Prebuilt LLVM 16.0.3 uploaded
Date: Wed, 3 May 2023 12:56:03 -0700 [thread overview]
Message-ID: <20230503195603.GA262195@dev-arch.thelio-3990X> (raw)
Hi all,
I have built and uploaded LLVM 16.0.3 to
https://mirrors.edge.kernel.org/pub/tools/llvm/.
As with 16.0.2, this release includes a fix relevant to the Linux
kernel, which you can read about here (thanks to Ard Biesheuvel for
helping debug and Nick Desaulniers for the fix):
https://github.com/llvm/llvm-project/commit/012ea747ed0275c499f69c82ac0f635f4c76f746
https://github.com/ClangBuiltLinux/linux/issues/1837
This issue is not super widespread but as always, I recommend using the
latest stable release of a piece of software whenever possible, so
consider using 16.0.3 in lieu of older 16.x releases. However, I
have shuffled the tarballs to a subdirectory to allow older versions of
these toolchains to be downloaded with more ease, which can be helpful
for tracking down regressions in warnings or code generation:
https://mirrors.edge.kernel.org/pub/tools/llvm/files/
Cheers,
Nathan
reply other threads:[~2023-05-03 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230503195603.GA262195@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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