| CARVIEW |
Navigation Menu
-
Notifications
You must be signed in to change notification settings - Fork 15.6k
Releases: llvm/llvm-project
LLVM 21.1.8
2078da4LLVM 21.1.8 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.8.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 65
- sha256:bb11319a6d31bb9a0123f909b3e06496240c4f580c516e9835f42b3252c3e0cd206 KB
2025-12-16T11:11:04Z - sha256:24af70b74f5c4b129b3aebfdaf54f115bd746e7f28b7f39ac702448f9d7a3dc3964 KB
2025-12-16T11:10:56Z - sha256:ef257afb8dede12b06411fb0eb90114c73d420e433735dbae8e4c55fe9fb2cd8119 Bytes
2025-12-16T11:11:00Z - sha256:f214b1226d8de005b5f691dd29d9dfea2b49e22d0de445429916173dbb626f7f1010 MB
2025-12-22T20:41:23Z - sha256:74bfc8513387777aed0683426ea6970acabec90348d96cdd30f619a51bf83d1d228 Bytes
2025-12-22T20:44:29Z - sha256:4c25b04275d7b34f47f6a7f8f05ef5518ab391c31c084e8f19e6a89a24f8fa571.46 GB
2025-12-22T20:36:50Z - sha256:510e395478c0e8620b70f5189f42f7d85265a6ba82a2208a39ce274274510c67228 Bytes
2025-12-22T20:41:21Z - sha256:749d22f565fcd5718dbed06512572d0e5353b502c03fe1f7f17ee8b8aca21a47899 MB
2025-12-17T13:08:47Z - sha256:938d958f214f2f4a628e9e5efb1995530afa2a00513917a1897ffc64f8a94b27543 Bytes
2025-12-17T13:09:26Z - sha256:6090e3f23720d003cdd84483a47d0eec6d01adbb5e0c714ac0c8b58de546aa6225.8 MB
2025-12-16T11:10:56Z -
2025-12-16T10:21:34Z -
2025-12-16T10:21:34Z - Loading
LLVM 21.1.7
LLVM 21.1.7 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.7.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 62
LLVM 21.1.6
a832a52LLVM 21.1.6 Release
-
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 either LLVM- or clang+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. 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:
<sub-project>-21.1.6.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 65
LLVM 21.1.5
c-rhodes
Cullen Rhodes
LLVM 21.1.5 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.5.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 63
LLVM 21.1.4
c-rhodes
Cullen Rhodes
LLVM 21.1.4 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.4.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 63
LLVM 21.1.3
450f52eLLVM 21.1.3 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.3.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 62
LLVM 21.1.2
tstellar
Tom Stellard
LLVM 21.1.2 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.2.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 62
LLVM 21.1.1
tru
Tobias Hieta
LLVM 21.1.1 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.1.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 64
LLVM 21.1.0
tru
Tobias Hieta
LLVM 21.1.0 Release
- 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 either LLVM- or clang+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. 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:
<sub-project>-21.1.0.src.tar.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)
Assets 63
LLVM 21.1.0-rc3
tru
Tobias Hieta
LLVM 21.1.0-rc3 Release
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-21.1.0-rc3-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 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-.
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.xzare archives of the sources of specific sub-projects ofllvm-project(except fortest-suitewhich is an archive of the LLVM Test Suite).- To get all the
llvm-projectsource 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 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)