GitHub Releases

Effortlessly track new versions of open source projects

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)

LLVM 22.1.0-rc3

LLVM 22.1.0-rc3 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-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 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-rc3.src.tar.xz.
  • test-suite-22.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 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-rc2

LLVM 22.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 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-rc2-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-rc2.src.tar.xz.
  • test-suite-22.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 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-rc1

LLVM 22.1.0-rc1 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-rc1-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>-22.1.0-rc1.src.tar.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-project-22.1.0-rc1.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)

LLVM 21.1.8

LLVM 21.1.8 Release

  • Linux x86_64 (signature)

  • Linux Arm64 (signature)

  • Linux Armv7-a (signature)

  • macOS Apple Silicon (ARM64) (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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
    • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.6

LLVM 21.1.6 Release

  • Linux x86_64 (signature)

  • Linux Arm64 (signature)

  • Linux Armv7-a (signature)

  • macOS Apple Silicon (ARM64) (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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
    • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.4

LLVM 21.1.4 Release

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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.3

LLVM 21.1.3 Release

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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.2

LLVM 21.1.2 Release

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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.1

LLVM 21.1.1 Release

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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.0

LLVM 21.1.0 Release

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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.0-rc3

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.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-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)

LLVM 21.1.0-rc2

LLVM 21.1.0-rc2 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-rc2-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-rc2.src.tar.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-project-21.1.0-rc2.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)

LLVM 21.1.0-rc1

LLVM 21.1.0-rc1 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-rc1-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-rc1.src.tar.xz are archives of the sources of specific sub-projects of llvm-project (except for test-suite which is an archive of the LLVM Test Suite).
  • To get all the llvm-project source code for this release, choose llvm-project-21.1.0-rc1.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)

LLVM 20.1.8

LLVM 20.1.8 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.7

LLVM 20.1.7 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.6

LLVM 20.1.6 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.5

LLVM 20.1.5 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.4

LLVM 20.1.4 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.3

LLVM 20.1.3 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.2

LLVM 20.1.2 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.1

LLVM 20.1.1 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.0

LLVM 20.1.0 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.0-rc3

LLVM 20.1.0-rc3 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.0-rc2

LLVM 20.1.0-rc2 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 20.1.0-rc1

LLVM 20.1.0-rc1 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.

LLVM 19.1.7

LLVM 19.1.7 Release

Announcement post: https://discourse.llvm.org/t/llvm-19-1-7-released/84062

LLVM 19.1.6

LLVM 19.1.6 Release

A note on binaries

Volunteers make binaries for the LLVM project, which will be uploaded when they have had time to test and build these binaries. They might not be available directly or not at all for each release. We suggest you use the binaries from your distribution or build your own if you rely on a specific platform or configuration.