@@ -20,15 +20,15 @@ cd src/llvm-project
20
20
git remote add my-target-llvm some-llvm-repository
21
21
git checkout my-target-llvm/my-branch
22
22
cd ..
23
- git add llvm_target
23
+ git add llvm-project
24
24
git commit -m 'Use my custom LLVM'
25
25
```
26
26
27
27
### Using pre-built LLVM
28
28
29
29
If you have a local LLVM checkout that is already built, you may be
30
- able to configure Rust to treat your build as the [ system LLVM] [ sysllvm ]
31
- to avoid redundant builds.
30
+ able to configure Rust to treat your build as the system LLVM to avoid
31
+ redundant builds.
32
32
33
33
You can tell Rust to use a pre-built version of LLVM using the ` target ` section
34
34
of ` config.toml ` :
@@ -74,7 +74,7 @@ You will need to add a line to the big table inside of the
74
74
will then add a corresponding file for your new target containing a
75
75
` target ` function.
76
76
77
- Look for existing targets to use as examples
77
+ Look for existing targets to use as examples.
78
78
79
79
## Patching crates
80
80
@@ -125,8 +125,10 @@ compiler, you can use it instead of the JSON file for both arguments.
125
125
## Promoting a target from tier 2 (target) to tier 2 (host)
126
126
127
127
There are two levels of tier 2 targets:
128
- a) Targets that are only cross-compiled (` rustup target add ` )
129
- b) Targets that have a native toolchain (` rustup toolchain install ` )
128
+ a) Targets that are only cross-compiled (` rustup target add ` )
129
+ b) Targets that [ have a native toolchain] [ tier2-native ] (` rustup toolchain install ` )
130
+
131
+ [ tier2-native ] : https://doc.rust-lang.org/nightly/rustc/target-tier-policy.html#tier-2-with-host-tools
130
132
131
133
For an example of promoting a target from cross-compiled to native,
132
134
see [ #75914 ] ( https://github.com/rust-lang/rust/pull/75914 ) .
0 commit comments