The Rust compiler uses LLVM as its primary codegen backend today, and naturally we want to at least occasionally update this dependency! Currently we do not have a strict policy about when to update LLVM or what it can be updated to, but a few guidelines are applied:
- We try to always support the latest released version of LLVM
- We try to support the "last few" versions of LLVM (how many is changing over time)
- We allow moving to arbitrary commits during development.
- Strongly prefer to upstream all patches to LLVM before including them in rustc.
This policy may change over time (or may actually start to exist as a formal policy!), but for now these are rough guidelines!
There are a few reasons nowadays that we want to update LLVM in one way or another:
A bug could have been fixed! Often we find bugs in the compiler and fix them upstream in LLVM. We'll want to pull fixes back to the compiler itself as they're merged upstream.
A new feature may be available in LLVM that we want to use in rustc, but we don't want to wait for a full LLVM release to test it out.
LLVM itself may have a new release and we'd like to update to this LLVM release.
Each of these reasons has a different strategy for updating LLVM, and we'll go over them in detail here.
For updates of LLVM that are to fix a small bug, we cherry-pick the bugfix to the branch we're already using. The steps for this are:
- Make sure the bugfix is in upstream LLVM.
- Identify the branch that rustc is currently using. The
src/llvm-projectsubmodule is always pinned to a branch of the rust-lang/llvm-project repository.
- Fork the rust-lang/llvm-project repository
- Check out the appropriate branch (typically named
- Cherry-pick the upstream commit onto the branch
- Push this branch to your fork
- Send a Pull Request to rust-lang/llvm-project to the same branch as before. Be sure to reference the Rust and/or LLVM issue that you're fixing in the PR description.
- Wait for the PR to be merged
- Send a PR to rust-lang/rust updating the
src/llvm-projectsubmodule with your bugfix. This can be done locally with
git submodule update --remote src/llvm-projecttypically.
- Wait for PR to be merged
The tl;dr; is that we can cherry-pick bugfixes at any time and pull them back into the rust-lang/llvm-project branch that we're using, and getting it into the compiler is just updating the submodule via a PR!
Example PRs look like: #59089
Note that this information is as of the time of this writing (April 2021). The process for updating LLVM changes with practically all LLVM updates, so this may be out of date!
Unlike bugfixes, updating to pick up a new feature of LLVM typically requires a lot more work. This is where we can't reasonably cherry-pick commits backwards so we need to do a full update. There's a lot of stuff to do here, so let's go through each in detail.
Create a new branch in the rust-lang/llvm-project repository. This branch should be named
a.bis the current version number of LLVM in-tree at the time of the branch and the remaining part is today's date. Move this branch to the commit in LLVM that you'd like, which for this is probably the current LLVM HEAD.
Apply Rust-specific patches to the llvm-project repository. All features and bugfixes are upstream, but there's often some weird build-related patches that don't make sense to upstream which we have on our repositories. These patches are around the latest patches in the rust-lang/llvm-project branch that rustc is currently using.
Build the new LLVM in the
rustrepository. To do this you'll want to update the
src/llvm-projectrepository to your branch and the revision you've created. It's also typically a good idea to update
.gitmoduleswith the new branch name of the LLVM submodule. Make sure you've committed changes to
src/llvm-projectto ensure submodule updates aren't reverted. Some commands you should execute are:
./x.py build src/llvm- test that LLVM still builds
./x.py build src/tools/lld- same for LLD
./x.py build- build the rest of rustc You'll likely need to update
llvm-wrapper/*.cppto compile with updated LLVM bindings. Note that you should use
#ifdefand such to ensure that the bindings still compile on older LLVM versions.
profile = "compiler"and other defaults set by
x.py setupdownload LLVM from CI instead of building it from source. You should disable this temporarily to make sure your changes are being used, by setting
[llvm] download-ci-llvm = false
Test for regressions across other platforms. LLVM often has at least one bug for non-tier-1 architectures, so it's good to do some more testing before sending this to bors! If you're low on resources you can send the PR as-is now to bors, though, and it'll get tested anyway.
Ideally, build LLVM and test it on a few platforms:
Windows and afterwards run some docker containers that CI also does:
Prepare a PR to
rust-lang/rust. Work with maintainers of
rust-lang/llvm-projectto get your commit in a branch of that repository, and then you can send a PR to
rust-lang/rust. You'll change at least
src/llvm-projectand will likely also change
For prior art, previous LLVM updates look like
#81451. Note that sometimes it's
easiest to land
llvm-wrapper compatibility as a PR before actually updating
src/llvm-project. This way while you're working through LLVM issues others
interested in trying out the new LLVM can benefit from work you've done to
update the C++ bindings.
Ideally the above instructions are pretty smooth, but here's some caveats to keep in mind while going through them:
- LLVM bugs are hard to find, don't hesitate to ask for help! Bisection is definitely your friend here (yes LLVM takes forever to build, yet bisection is still your friend)
- If you've got general questions, wg-llvm can help you out.
- Creating branches is a privileged operation on GitHub, so you'll need someone with write access to create the branches for you most likely.
Updating to a new release of LLVM is very similar to the "feature updates" section above. The release process for LLVM is often months-long though and we like to ensure compatibility ASAP. The main tweaks to the "feature updates" section above is generally around branch naming. The sequence of events typically looks like:
LLVM announces that its latest release version has branched. This will show up as a branch in https://github.com/llvm/llvm-project typically named
$Nis the version of LLVM that's being released.
We then follow the "feature updates" section above to create a new branch of LLVM in our rust-lang/llvm-project repository. This follows the same naming convention of branches as usual, except that
a.bis the new version. This update is eventually landed in the rust-lang/rust repository.
Over the next few months, LLVM will continually push commits to its
release/a.bbranch. Often those are bug fixes we'd like to have as well. The merge process for that is to use
git mergeitself to merge LLVM's
release/a.bbranch with the branch created in step 2. This is typically done multiple times when necessary while LLVM's release branch is baking.
LLVM then announces the release of version
After LLVM's official release, we follow the "feature update" section again to create a new branch in the rust-lang/llvm-project repository, this time with a new date. The commit history should look much cleaner as just a few Rust-specific commits stacked on top of stock LLVM's release branch.