user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

reflow

Browse source
This commit is contained in:
Tshepang Mbambo 2026-02-03 00:47:52 +02:00
parent 222e5216a0
commit 670fec6bbd
3 changed files with 5 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

3
src/doc/rustc-dev-guide/src/building/new-target.md
View file

@ -72,8 +72,7 @@ somewhat successfully, you can copy the specification into the compiler itself.
You will need to add a line to the big table inside of the
`supported_targets` macro in the `rustc_target::spec` module.
You will then add a corresponding file for your new target containing a
`target` function.
You will then add a corresponding file for your new target containing a `target` function.
Look for existing targets to use as examples.

5
src/doc/rustc-dev-guide/src/building/optimized-build.md
View file

@ -55,9 +55,8 @@ rust.codegen-units-std = 1
By default, `rustc` is compiled for a generic (and conservative) instruction set architecture
(depending on the selected target), to make it support as many CPUs as possible.
If you want to
compile `rustc` for a specific instruction set architecture, you can set the `target_cpu` compiler
option in `RUSTFLAGS`:
If you want to compile `rustc` for a specific instruction set architecture,
you can set the `target_cpu` compiler option in `RUSTFLAGS`:
```bash
RUSTFLAGS="-C target_cpu=x86-64-v3" ./x build ...

6
src/doc/rustc-dev-guide/src/building/suggested.md
View file

@ -118,8 +118,7 @@ requires extra disk space.
Selecting `vscode` in `./x setup editor` will prompt you to create a
`.vscode/settings.json` file which will configure Visual Studio code.
The recommended `rust-analyzer` settings live at
[`src/etc/rust_analyzer_settings.json`].
The recommended `rust-analyzer` settings live at [`src/etc/rust_analyzer_settings.json`].
If running `./x check` on save is inconvenient, in VS Code you can use a [Build Task] instead:
@ -253,8 +252,7 @@ It can be configured through `.zed/settings.json`, as described
[here](https://zed.dev/docs/configuring-languages).
Selecting `zed` in `./x setup editor` will prompt you to create a `.zed/settings.json`
file which will configure Zed with the recommended configuration.
The recommended `rust-analyzer` settings live
at [`src/etc/rust_analyzer_zed.json`].
The recommended `rust-analyzer` settings live at [`src/etc/rust_analyzer_zed.json`].
## Check, check, and check again