mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Warn users about limited review for tier 2 and 3 code

Browse Source
This commit is contained in:
Mark Rousskov 2024-01-20 16:22:02 -05:00
parent 6745c6000a
commit cc8e56b1e9
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
src/doc/rustc/src/platform-support.md
View File

@ -72,6 +72,12 @@ ensure that each tier 2 target can be used as build target after each change. Au
not always run so it's not guaranteed to produce a working build, but tier 2 not always run so it's not guaranteed to produce a working build, but tier 2
targets often work to quite a good degree and patches are always welcome! targets often work to quite a good degree and patches are always welcome!
Tier 2 target-specific code is not closely scrutinized by Rust team(s) when
modifications are made. Bugs are possible in all code, but the level of quality
control for these targets is likely to be lower. See [library team
policy](https://std-dev-guide.rust-lang.org/policy/target-code.html) for
details on the review practices for standard library code.
Tier 2 targets with host tools additionally support running tools like `rustc` Tier 2 targets with host tools additionally support running tools like `rustc`
and `cargo` natively on the target, and automated builds ensure that the host and `cargo` natively on the target, and automated builds ensure that the host
tools build as well. This allows the target to be used as a development tools build as well. This allows the target to be used as a development
@ -121,6 +127,12 @@ The `std` column in the table below has the following meanings:
[`no_std`]: https://rust-embedded.github.io/book/intro/no-std.html [`no_std`]: https://rust-embedded.github.io/book/intro/no-std.html
Tier 2 target-specific code is not closely scrutinized by Rust team(s) when
modifications are made. Bugs are possible in all code, but the level of quality
control for these targets is likely to be lower. See [library team
policy](https://std-dev-guide.rust-lang.org/policy/target-code.html) for
details on the review practices for standard library code.
**NOTE:** The `rust-docs` component is not usually built for tier 2 targets, **NOTE:** The `rust-docs` component is not usually built for tier 2 targets,
so Rustup may install the documentation for a similar tier 1 target instead. so Rustup may install the documentation for a similar tier 1 target instead.
@ -211,6 +223,12 @@ The `std` column in the table below has the following meanings:
[`no_std`]: https://rust-embedded.github.io/book/intro/no-std.html [`no_std`]: https://rust-embedded.github.io/book/intro/no-std.html
Tier 3 target-specific code is not closely scrutinized by Rust team(s) when
modifications are made. Bugs are possible in all code, but the level of quality
control for these targets is likely to be lower. See [library team
policy](https://std-dev-guide.rust-lang.org/policy/target-code.html) for
details on the review practices for standard library code.
The `host` column indicates whether the codebase includes support for building The `host` column indicates whether the codebase includes support for building
host tools. host tools.