https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try 2025-10-02T23:16:26+00:00 2025-10-02T23:16:26+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-10-02T23:16:26+00:00 urn:sha1:a3291ede1a28a79c37c296bd021939751f69969a make rust-analyzer use a dedicated build directory inspired by https://github.com/rust-lang/rust/pull/132794 2025-10-01T12:15:00+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-10-01T12:15:00+00:00 urn:sha1:62b72bd545d2caff23164732aa881ff6e169005d Replace `rustc_span::Span` with a stripped down version for librustdoc's highlighter While profiling rustdoc's syntax highlighter, I noticed a lot of time being spent in the `Span` interner, due to the highlighter creating a lot of (new) spans. Since the only data from the `Span` that we use is the `hi` and `lo` byte positions - I replaced the regular `Span` with a simple one with two fields, and in my benchmarks it seemed to make a big dent in the highlighter's perf, so thought I would see what the perf runner says. 2025-10-01T12:15:00+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-10-01T12:15:00+00:00 urn:sha1:ca8ed7eb805f9be8767077510c9685cc692dd032 Remove usage of `compiletest-use-stage0-libtest` from CI It shouldn't be needed anymore after https://github.com/rust-lang/rust/pull/146929. r? `@Zalathar` 2025-09-30T18:46:46+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-09-30T18:46:46+00:00 urn:sha1:4cbaa701012bf646185f924980d0fd5fb65b925c bootstrap: build bootstrap docs with in-tree rustdoc All of the docs need to be built with the same rustdoc. Otherwise, any change to the search index breaks everything, because the two rustdocs don't agree on the format. Fixes https://github.com/rust-lang/rust/issues/147142 2025-09-30T18:13:45+00:00 Yotam Ofek yotam.ofek@gmail.com 2025-09-29T21:14:03+00:00 urn:sha1:6edf05b740070429e57ec18e5c027167dbb17ab4 2025-09-30T15:31:08+00:00 Michael Howell michael@notriddle.com 2025-09-30T04:02:52+00:00 urn:sha1:ba13b6ec6f919430412d99a3d50ff87042a787a7 All of the docs need to be built with the same rustdoc. Otherwise, any change to the search index breaks everything, because the two rustdocs don't agree on the format. 2025-09-30T14:08:48+00:00 Jakub Beránek berykubik@gmail.com 2025-09-30T14:08:48+00:00 urn:sha1:5f54d8bfd8e5921dc5eb5bbe0799907ed4ca1916 2025-09-29T23:02:22+00:00 Jynn Nelson jynn.nelson@ferrous-systems.com 2025-09-22T17:59:39+00:00 urn:sha1:73f6b08022944d24fb5b623494a18cc95df21802 In d94e7ff065cd393a645eb3e9c96ce0418856e95d, `rustdoc_path` was changed to ignore `want_rustdoc` (which is just whether `--no-doc` was passed). But RUSTDOC_LIBDIR wasn't kept in sync. Rather than trying to keep `rustdoc_path` in sync with `RUSTDOC_LIBDIR`, just pass LIBDIR to the rustc shim unconditionally. This fix allows calling `ensure(doc::Step)` from a non-doc top-level Step, even if `--no-doc` was present in the command line. 2025-09-29T01:56:41+00:00 Stuart Cook Zalathar@users.noreply.github.com 2025-09-29T01:56:41+00:00 urn:sha1:3ea1bab98225515049b90c9dcb53a88d1451874a compiletest: Remove old-output-capture and become a stage0 bootstrap tool The new compiletest output-capture system became the default in rust-lang/rust#146574, and no problems have been reported since. This PR therefore removes the old output-capture implementation from compiletest, and adjusts bootstrap to always build and test compiletest as a stage0 bootstrap tool. In other words, compiletest no longer relies on any unstable features (such as `libtest` or `internal_output_capture`), and is now written entirely in stable Rust! The compiletest self-tests still need access to an in-tree rustc, in order to obtain information via `rustc --print`, so we interpret `--stage` as indicating the stage of that secondary compiler, but always use the stage0 compiler to build compiletest itself. r? Kobzol 2025-09-28T07:18:07+00:00 Zalathar Zalathar@users.noreply.github.com 2025-09-23T12:05:12+00:00 urn:sha1:8b1879864b4487c89ee414fa64abe42440fa922b