Skip to content

Commit 7c5f59a

Browse files
committed
reflow
1 parent 9396555 commit 7c5f59a

3 files changed

Lines changed: 5 additions & 9 deletions

File tree

src/building/new-target.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,8 +72,7 @@ somewhat successfully, you can copy the specification into the compiler itself.
7272

7373
You will need to add a line to the big table inside of the
7474
`supported_targets` macro in the `rustc_target::spec` module.
75-
You will then add a corresponding file for your new target containing a
76-
`target` function.
75+
You will then add a corresponding file for your new target containing a `target` function.
7776

7877
Look for existing targets to use as examples.
7978

src/building/optimized-build.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,8 @@ rust.codegen-units-std = 1
5555

5656
By default, `rustc` is compiled for a generic (and conservative) instruction set architecture
5757
(depending on the selected target), to make it support as many CPUs as possible.
58-
If you want to
59-
compile `rustc` for a specific instruction set architecture, you can set the `target_cpu` compiler
60-
option in `RUSTFLAGS`:
58+
If you want to compile `rustc` for a specific instruction set architecture,
59+
you can set the `target_cpu` compiler option in `RUSTFLAGS`:
6160

6261
```bash
6362
RUSTFLAGS="-C target_cpu=x86-64-v3" ./x build ...

src/building/suggested.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -118,8 +118,7 @@ requires extra disk space.
118118

119119
Selecting `vscode` in `./x setup editor` will prompt you to create a
120120
`.vscode/settings.json` file which will configure Visual Studio code.
121-
The recommended `rust-analyzer` settings live at
122-
[`src/etc/rust_analyzer_settings.json`].
121+
The recommended `rust-analyzer` settings live at [`src/etc/rust_analyzer_settings.json`].
123122

124123
If running `./x check` on save is inconvenient, in VS Code you can use a [Build Task] instead:
125124

@@ -253,8 +252,7 @@ It can be configured through `.zed/settings.json`, as described
253252
[here](https://zed.dev/docs/configuring-languages).
254253
Selecting `zed` in `./x setup editor` will prompt you to create a `.zed/settings.json`
255254
file which will configure Zed with the recommended configuration.
256-
The recommended `rust-analyzer` settings live
257-
at [`src/etc/rust_analyzer_zed.json`].
255+
The recommended `rust-analyzer` settings live at [`src/etc/rust_analyzer_zed.json`].
258256

259257
## Check, check, and check again
260258

0 commit comments

Comments
 (0)