LLVM 21.1.8 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)

• macOS Apple Silicon (ARM64) (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.8-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.8.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.8.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.7 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.7-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.7.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.7.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.6 Release

• Linux x86_64 (signature)

• Linux Arm64 (signature)

• Linux Armv7-a (signature)

• macOS Apple Silicon (ARM64) (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.6-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.6.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.6.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.5 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.5-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.5.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.5.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.4 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.4-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.4.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.4.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.3 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.3-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.3.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.3.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.2 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.2-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.2.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.2.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.1 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.1-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.1.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.1.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.0 Release

• Linux x86_64 (signature)
• Linux Arm64 (signature)
• Linux Armv7-a (signature)

• Windows x64 (64-bit):installer (signature),archive (signature)
• Windows x86 (32-bit):installer (signature)
• Windows on Arm (ARM64):installer (signature),archive (signature)

For any other variants of platform and architecture, check the full list of release packages at the bottom of this release page. If you do not find a release package for your platform, you may be able to find a community built package on theLLVM 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 eitherLLVM- orclang+llvm- and ends with the platform's name. For example,LLVM-21.1.0-Linux-ARM64.tar.xz contains LLVM binaries for Arm64 Linux.

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

In addition, source archives are available:

• <sub-project>-21.1.0.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.0.src.tar.xz.

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 theLLVM 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, usegh 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)

LLVM 21.1.0-rc3 Release

Package Types

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

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

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.

In addition, source archives are available:

• <sub-project>-21.1.0-rc3.src.tar.xz are archives of the sources of specific sub-projects ofllvm-project (except fortest-suite which is an archive of theLLVM Test Suite).
• To get all thellvm-project source code for this release, choosellvm-project-21.1.0-rc3.src.tar.xz.

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 theLLVM 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, usegh 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)