mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

numbers were not sequential, so stop trying

This commit is contained in:
Tshepang Mbambo 2025-03-08 20:33:05 +02:00
parent 3684751c90
commit 723b887eff
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/backend/updating-llvm.md
View File

@ -116,14 +116,14 @@ so let's go through each in detail.
at the time of the branch, at the time of the branch,
and the remaining part is the current date. and the remaining part is the current date.
2. Apply Rust-specific patches to the llvm-project repository. 1. Apply Rust-specific patches to the llvm-project repository.
All features and bugfixes are upstream, All features and bugfixes are upstream,
but there's often some weird build-related patches but there's often some weird build-related patches
that don't make sense to upstream. that don't make sense to upstream.
These patches are typically the latest patches in the These patches are typically the latest patches in the
rust-lang/llvm-project branch that rustc is currently using. rust-lang/llvm-project branch that rustc is currently using.
3. Build the new LLVM in the `rust` repository. 1. Build the new LLVM in the `rust` repository.
To do this, To do this,
you'll want to update the `src/llvm-project` repository to your branch, you'll want to update the `src/llvm-project` repository to your branch,
and the revision you've created. and the revision you've created.
@ -151,7 +151,7 @@ so let's go through each in detail.
download-ci-llvm = false download-ci-llvm = false
``` ```
4. Test for regressions across other platforms. LLVM often has at least one bug 1. 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 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 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. now to bors, though, and it'll get tested anyway.
@ -170,7 +170,7 @@ so let's go through each in detail.
* `./src/ci/docker/run.sh dist-various-2` * `./src/ci/docker/run.sh dist-various-2`
* `./src/ci/docker/run.sh armhf-gnu` * `./src/ci/docker/run.sh armhf-gnu`
5. Prepare a PR to `rust-lang/rust`. Work with maintainers of 1. Prepare a PR to `rust-lang/rust`. Work with maintainers of
`rust-lang/llvm-project` to get your commit in a branch of that repository, `rust-lang/llvm-project` to 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 and then you can send a PR to `rust-lang/rust`. You'll change at least
`src/llvm-project` and will likely also change [`llvm-wrapper`] as well. `src/llvm-project` and will likely also change [`llvm-wrapper`] as well.
@ -194,7 +194,7 @@ so let's go through each in detail.
others interested in trying out the new LLVM can benefit from work you've done others interested in trying out the new LLVM can benefit from work you've done
to update the C++ bindings. to update the C++ bindings.
3. Over the next few months, 1. Over the next few months,
LLVM will continually push commits to its `release/a.b` branch. LLVM will continually push commits to its `release/a.b` branch.
We will often want to have those bug fixes as well. We will often want to have those bug fixes as well.
The merge process for that is to use `git merge` itself to merge LLVM's The merge process for that is to use `git merge` itself to merge LLVM's
@ -202,9 +202,9 @@ so let's go through each in detail.
This is typically This is typically
done multiple times when necessary while LLVM's release branch is baking. done multiple times when necessary while LLVM's release branch is baking.
4. LLVM then announces the release of version `a.b`. 1. LLVM then announces the release of version `a.b`.
5. After LLVM's official release, 1. After LLVM's official release,
we follow the process of creating a new branch on the we follow the process of creating a new branch on the
rust-lang/llvm-project repository again, rust-lang/llvm-project repository again,
this time with a new date. this time with a new date.