LLVM

Languages & Runtimes

A collection of modular compiler and toolchain technologies.

Latest llvmorg-22.1.8 · by LLVM FoundationWebsitellvm/llvm-project

Release activity

Release activity — 10 releases across 10 days since Feb 24, 2026. Each cell is one day; darker means more releases that day. Nothing is recorded before Feb 24, 2026. Older weeks are hidden at this screen width.
MayJunJulAug
SundayNo releases on Apr 19, 2026No releases on Apr 26, 2026No releases on May 3, 2026No releases on May 10, 2026No releases on May 17, 2026No releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026
MondayNo releases on Apr 20, 2026No releases on Apr 27, 2026No releases on May 4, 2026No releases on May 11, 2026No releases on May 18, 2026No releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026
Tuesday1 release on Apr 21, 2026No releases on Apr 28, 20261 release on May 5, 2026No releases on May 12, 20261 release on May 19, 2026No releases on May 26, 20261 release on Jun 2, 2026No releases on Jun 9, 20261 release on Jun 16, 2026No releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 2026No releases on Jul 21, 20261 release on Jul 28, 2026No releases on Aug 4, 2026
WednesdayNo releases on Apr 22, 2026No releases on Apr 29, 2026No releases on May 6, 2026No releases on May 13, 2026No releases on May 20, 2026No releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026
ThursdayNo releases on Apr 23, 2026No releases on Apr 30, 2026No releases on May 7, 2026No releases on May 14, 2026No releases on May 21, 2026No releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026
FridayNo releases on Apr 24, 2026No releases on May 1, 2026No releases on May 8, 2026No releases on May 15, 2026No releases on May 22, 2026No releases on May 29, 2026No releases on Jun 5, 2026No releases on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026
SaturdayNo releases on Apr 25, 2026No releases on May 2, 2026No releases on May 9, 2026No releases on May 16, 2026No releases on May 23, 2026No releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026

10 releases since Feb 24, 2026

Changelog

llvmorg-23.1.0-rc2Pre-release

LLVM 23.1.0-rc2

LLVM 23.1.0-rc2 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has binary release packages. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-23.1.0-rc2-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux. Binary archive packages may be available as .tar.xz or .tar.zst files. The .tar.zst files contain the same package contents, but use zstd compression.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-23.1.0-rc2.src.tar.xz.
  • test-suite-23.1.0-rc2.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-23.1.0-rc2 went
llvmorg-22.1.8

LLVM 22.1.8

LLVM 22.1.8 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.8-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.8.src.tar.xz.
  • test-suite-22.1.8.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.8 went
llvmorg-22.1.7

LLVM 22.1.7

LLVM 22.1.7 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.7-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.7.src.tar.xz.
  • test-suite-22.1.7.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.7 went
llvmorg-22.1.6

LLVM 22.1.6

LLVM 22.1.6 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.6-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.6.src.tar.xz.
  • test-suite-22.1.6.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.6 went
llvmorg-22.1.5

LLVM 22.1.5

LLVM 22.1.5 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.5-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.5.src.tar.xz.
  • test-suite-22.1.5.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.5 went
llvmorg-22.1.4

LLVM 22.1.4

LLVM 22.1.4 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.4-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.4.src.tar.xz.
  • test-suite-22.1.4.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.4 went
llvmorg-22.1.3

LLVM 22.1.3

LLVM 22.1.3 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.3-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.3.src.tar.xz.
  • test-suite-22.1.3.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.3 went
llvmorg-22.1.2

LLVM 22.1.2

LLVM 22.1.2 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.2-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.2.src.tar.xz.
  • test-suite-22.1.2.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.2 went
llvmorg-22.1.1

LLVM 22.1.1

LLVM 22.1.1 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.1-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.1.src.tar.xz.
  • test-suite-22.1.1.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig and/or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.1 went
llvmorg-22.1.0

LLVM 22.1.0

LLVM 22.1.0 Release

Download links for common platforms will appear above once builds have completed, if they are available. Check the full list of release packages at the bottom of this release page if you do not find a link above.

If you do not find a release package for your platform, you may be able to find a community built package on the LLVM Discourse forum thread for this release. Remember that these are built by volunteers and may not always be available. If you rely on a platform or configuration that is not one of the defaults, we suggest you use the binaries that your platform provides, or build your own release packages.

Package Types

Each platform has one binary release package. The file name starts with either LLVM- or clang+llvm- and ends with the platform's name. For example, LLVM-22.1.0-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

Except for Windows. Where LLVM-*.exe is an installer intended for using LLVM as a toolchain and the archive clang+llvm- contains the contents of the installer, plus libraries and tools not normally used in a toolchain. You most likely want the LLVM- installer, unless you are developing software which itself uses LLVM, in which case choose clang+llvm-.

In addition, source archives are available:

  • To get all the llvm-project source code for this release, choose llvm-project-22.1.0.src.tar.xz.
  • test-suite-22.1.0.src.tar.xz is an archive of the LLVM Test Suite) for this release.
Verifying Packages

All packages come with a matching .sig or .jsonl file. You should use these to verify the integrity of the packages.

If it has a .sig file, it should have been signed by the release managers using GPG. Download the keys from the LLVM website, import them into your keyring and use them to verify the file:

$ gpg --import release-keys.asc
$ gpg --verify <package file name>.sig <package file name>

If it has a .jsonl file, use gh to verify the package:

$ gh attestation verify --repo llvm/llvm-project <package file name>
(if you are able to connect to GitHub)
$ gh attestation verify --repo llvm/llvm-project <package file name> --bundle <package file name>.jsonl
(using attestation file on disk)
View originalPermalink
How llvmorg-22.1.0 went

More in Languages & Runtimes

View all
node

Open-source, cross-platform JavaScript runtime environment

node
TypeScript

JavaScript with syntax for types.

Microsoft
Go

An open-source language for building simple, reliable, and efficient software.

Google
mise

mise release notes.

mise
css-select

css-select release notes.

css-select
RxJava

RxJava release notes.

RxJava

Discussion