Skip to content

Commit 057f15e

Browse files
committed
sample output
1 parent 86136ba commit 057f15e

File tree

1 file changed

+10
-6
lines changed
  • src/doc/rustc-dev-guide/src/tests/codegen-backend-tests

1 file changed

+10
-6
lines changed

src/doc/rustc-dev-guide/src/tests/codegen-backend-tests/cg_gcc.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,8 @@ you can use the following command to run UI tests locally using the GCC backend,
2121

2222
If a different test suite has failed on CI, you will have to modify the `tests/ui` part.
2323

24-
To reproduce the whole CI job locally, you can run `cargo run --manifest-path src/ci/citool/Cargo.toml run-local x86_64-gnu-gcc`. See [Testing with Docker](../docker.md) for more information.
24+
To reproduce the whole CI job locally, you can run `cargo run --manifest-path src/ci/citool/Cargo.toml run-local x86_64-gnu-gcc`.
25+
See [Testing with Docker](../docker.md) for more information.
2526

2627
### What to do in case of a GCC job failure?
2728

@@ -32,23 +33,25 @@ If fixing a compiler test that fails with the GCC backend is non-trivial, you ca
3233
## Choosing which codegen backends are built
3334

3435
The `rust.codegen-backends = [...]` bootstrap option affects which codegen backends will be built and
35-
included in the sysroot of the produced `rustc`. To use the GCC codegen backend, `"gcc"` has to
36-
be included in this array in `bootstrap.toml`:
36+
included in the sysroot of the produced `rustc`.
37+
To use the GCC codegen backend, `"gcc"` has to be included in this array in `bootstrap.toml`:
3738

3839
```toml
3940
rust.codegen-backends = ["llvm", "gcc"]
4041
```
4142

4243
If you don't want to change your `bootstrap.toml` file, you can alternatively run your `x`
43-
commands with `--set 'rust.codegen-backends=["llvm", "gcc"]'`. For example:
44+
commands with `--set 'rust.codegen-backends=["llvm", "gcc"]'`.
45+
For example:
4446

4547
```bash
4648
./x build --set 'rust.codegen-backends=["llvm", "gcc"]'
4749
```
4850

4951
The first backend in the `codegen-backends` array will determine which backend will be used as the
5052
*default backend* of the built `rustc`. This also determines which backend will be used to compile the
51-
stage 1 standard library (or anything built in stage 2+). To produce `rustc` that uses the GCC backend
53+
stage 1 standard library (or anything built in stage 2+).
54+
To produce `rustc` that uses the GCC backend
5255
by default, you can thus put `"gcc"` as the first element of this array:
5356

5457
```bash
@@ -69,7 +72,8 @@ Note that in order for this to work, the tested compiler must have the GCC codeg
6972
## Downloading GCC from CI
7073

7174
The `gcc.download-ci-gcc` bootstrap option controls if GCC (which is a dependency of the GCC codegen backend)
72-
will be downloaded from CI or built locally. The default value is `true`, which will download GCC from CI
75+
will be downloaded from CI or built locally.
76+
The default value is `true`, which will download GCC from CI
7377
if there are no local changes to the GCC sources and the given host target is available on CI.
7478

7579
## Running tests of the backend itself

0 commit comments

Comments
 (0)