Skip to content

Commit

Permalink
Improve wording
Browse files Browse the repository at this point in the history
Co-authored-by: LeSeulArtichaut <leseulartichaut@gmail.com>
  • Loading branch information
jyn514 and LeSeulArtichaut authored Oct 1, 2020
1 parent 3c1c162 commit abcd2bc
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/building/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -184,7 +184,7 @@ Note that there are two `std` libraries in play here:
2. The library _used to compile programs_ with `stageN/rustc`, which was
built by stage N (stage N `std`).

stage N `std` is pretty much necessary for any useful work with the stage N compiler.
Stage N `std` is pretty much necessary for any useful work with the stage N compiler.
Without it, you can only compile programs with `#![no_core]` -- not terribly useful!

The reason these need to be different is because they aren't necessarily ABI-compatible:
Expand All @@ -194,7 +194,7 @@ to Rust metadata on nightly that aren't present in beta.
This is also where `--keep-stage 1 library/std` comes into play. Since most
changes to the compiler don't actually change the ABI, once you've produced a
`std` in stage 1, you can probably just reuse it with a different compiler.
If the ABI hasn't changed, you're good to go, no need to spend the time
If the ABI hasn't changed, you're good to go, no need to spend time
recompiling that `std`.
`--keep-stage` simply assumes the previous compile is fine and copies those
artifacts into the appropriate place, skipping the cargo invocation.
Expand Down

0 comments on commit abcd2bc

Please sign in to comment.