rust/src/doc/rustc, branch 1.84.0

Correct the tier listing of `wasm32-wasip2`

2024-11-19T15:56:34+00:00

This target is tier 2, not tier 3, and I forgot to update this. Closes #133206

Update src/doc/rustc/src/platform-support/s390x-unknown-linux-gnu.md

2024-11-18T20:31:39+00:00

Co-authored-by: Josh Stone

Document s390x-unknown-linux targets

2024-11-18T18:44:25+00:00

This adds documentation for the following existing targets: s390x-unknown-linux-gnu (Tier 2 with host tools) s390x-unknown-linux-musl (Tier 3) I volunteer as maintainer for these targets going forward. Signed-off-by: Ulrich Weigand

Remove the `wasm32-wasi` target from rustc

2024-11-03T15:09:34+00:00

This commit is the final step in the journey of renaming the historical `wasm32-wasi` target in the Rust compiler to `wasm32-wasip1`. Various steps in this journey so far have been: * 2023-04-03: rust-lang/compiler-team#607 - initial proposal for this rename * 2024-11-27: rust-lang/compiler-team#695 - amended schedule/procedure for rename * 2024-01-29: rust-lang/rust#120468 - initial introduction of `wasm32-wasip1` * 2024-06-18: rust-lang/rust#126662 - warn on usage of `wasm32-wasi` * 2024-11-08: this PR - remove the `wasm32-wasi` target The full transition schedule is in [this comment][comment] and is summarized with: * 2024-05-02: Rust 1.78 released with `wasm32-wasip1` target * 2024-09-05: Rust 1.81 released warning on usage of `wasm32-wasi` * 2025-01-09: Rust 1.84 to be released without the `wasm32-wasi` target This means that support on stable for the replacement target of `wasm32-wasip1` has currently been available for 6 months. Users have already seen warnings on stable for 2 months about usage of `wasm32-wasi` and stable users have another 2 months of warnings before the target is removed from stable. This commit is intended to be the final step in this transition so the source tree should no longer mention `wasm32-wasi` except in historical reference to the older name of the `wasm32-wasip1` target. [comment]: https://github.com/rust-lang/rust/pull/120468#issuecomment-1977878747

Add `--print host-triple`

2024-11-02T20:29:59+00:00

People often parse `-vV` output to get to the host triple, which is annoying to do. It's easier to just get it directly.

Rollup merge of #131829 - Zalathar:goodbye-zprofile, r=chenyukang

2024-11-01T19:08:49+00:00

Remove support for `-Zprofile` (gcov-style coverage instrumentation) Tracking issue: #42524 MCP: https://github.com/rust-lang/compiler-team/issues/798 --- This PR removes the unstable `-Zprofile` flag, which enables ”gcov-style” coverage instrumentation, along with its associated `-Zprofile-emit` configuration flag. (The profile flag predates and is almost entirely separate from the stable `-Cinstrument-coverage` flag.) Notably, the `-Zprofile` flag: - Is largely untested in-tree, having only one run-make test that does not check whether its output is correct or useful. - Has no known maintainer. - Has seen no push towards stabilization. - Has at least one severe regression reported in 2022 that apparently remains unaddressed. - #100125 - Is confusingly named, since it appears to be more about coverage than performance profiling, and has nothing to do with PGO. - Is fundamentally limited by relying on counters auto-inserted by LLVM, with no knowledge of Rust beyond debuginfo.

Document the difference between Clang's `-darwin` and `-macosx` targets

2024-10-31T17:20:57+00:00

Remove support for `-Zprofile` (gcov-style coverage instrumentation)

2024-10-30T22:09:25+00:00

Rollup merge of #132327 - djkoloski:redirect_fuchsia_maintainers, r=compiler-errors

2024-10-30T05:40:36+00:00

Point to Fuchsia team in platform support docs This consolidates our docs into a single source of truth for the current Fuchsia maintainers. r? ```@tmandry```

Rollup merge of #132322 - daltenty:daltenty/update-aix-maintainters, r=workingjubilee

2024-10-30T05:40:35+00:00

powerpc64-ibm-aix: update maintainters Chaofan (`@ecnelises)` and Kai (`@bzEq)` will be passing over maintainership for the target over to David Tenty (`@daltenty)` and Chris Cambly (`@gilamn5tr)`