LLVM

LLVM 23.1.1 Release

• Linux x86_64: xz archive (signature), zstd archive (signature)
• Linux Arm64: xz archive (signature), zstd archive (signature)

• macOS Apple Silicon (ARM64): xz archive (signature), zstd archive (signature)

• Windows x64 (64-bit): installer (signature), xz archive (signature), zstd archive (signature)

• Windows on Arm (ARM64): installer (signature), xz archive (signature), zstd archive (signature)

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.1-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-*.msi 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.1.src.tar.xz.
• test-suite-23.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)

LLVM 23.1.0 Release

• Linux x86_64: xz archive (signature), zstd archive (signature)
• Linux Arm64: xz archive (signature), zstd archive (signature)

• Windows x64 (64-bit): installer (signature), xz archive (signature), zstd archive (signature)

• Windows on Arm (ARM64): installer (signature), xz archive (signature), zstd archive (signature)

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-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-*.msi 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.src.tar.xz.
• test-suite-23.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 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)

LLVM 23.1.0-rc3 Release

• Linux x86_64: xz archive (signature), zstd archive (signature)
• Linux Arm64: xz archive (signature), zstd archive (signature)

• macOS Apple Silicon (ARM64): xz archive (signature), zstd archive (signature)

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-rc3-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-rc3.src.tar.xz.
• test-suite-23.1.0-rc3.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)

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)

LLVM 22.1.8 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.7 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.6 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.5 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.4 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.3 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.2 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.1 Release

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

• macOS Apple Silicon (ARM64) (signature)

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

• Windows on Arm (ARM64): installer (signature), archive (signature)

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)

LLVM 22.1.0 Release

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

• macOS Apple Silicon (ARM64) (signature)

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)