rust/src/ci, branch try-perfhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try-perf2025-10-03T08:43:43+00:00Auto merge of #145898 - lolbinarycat:rustdoc-search-trait-parent, r=GuillaumeGomez,notriddle2025-10-03T08:43:43+00:00borsbors@rust-lang.org2025-10-03T08:43:43+00:00urn:sha1:dd091003ace19d9556c647d87f7a9cd1e8dcc17e
If a trait item appears in rustdoc search, hide the corrosponding impl items
fixes rust-lang/rust#138251
cc `@notriddle`
rustdoc: use same stage for all pr check docs2025-10-02T20:29:36+00:00Michael Howellmichael@notriddle.com2025-10-02T17:19:42+00:00urn:sha1:c7d6857f750a8c957ebca81340faa379cc3d110fRollup merge of #147233 - GuillaumeGomez:citool-submodule-init, r=Kobzol2025-10-02T08:27:53+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-10-02T08:27:53+00:00urn:sha1:f4dcfa6ddb36eaecd5c9320ba9fb24ad45468052
Initialize llvm submodule if not already the case to run citool
While working on https://github.com/rust-lang/rust/pull/146414, I ran the following command (to run CI docker locally):
```
cargo run --manifest-path src/ci/citool/Cargo.toml run-local --type pr x86_64-gnu-gcc
```
However, since I didn't have `src/llvm` submodule initialized, it failed. Apparently it's a common issue for people using this tool so this PR removes this small inconvenience.
r? ``@Kobzol``
Initialize llvm submodule if not already the case to run citool2025-10-01T15:38:36+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-10-01T15:38:36+00:00urn:sha1:4baf9208a129e5ea8b3973ce2eeb55fdd7404aeaSwitch `citool` to 2024 edition2025-10-01T15:36:53+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-10-01T15:36:53+00:00urn:sha1:69619535d9dbad6a7f5e622bfd3e3c3fb190e0aaRemove usage of `compiletest-use-stage0-libtest` from CI2025-09-30T14:08:48+00:00Jakub Beránekberykubik@gmail.com2025-09-30T14:08:48+00:00urn:sha1:5f54d8bfd8e5921dc5eb5bbe0799907ed4ca1916Make macOS dist build configuration match where reasonable2025-09-29T12:52:09+00:00Jake Gouldingjake.goulding@gmail.com2025-08-26T12:52:54+00:00urn:sha1:5df0be398845fa8b239f3e722c25b8369498df5cAuto merge of #146513 - madsmtm:apple-reenable-assertions, r=Mark-Simulacrum2025-09-28T21:40:04+00:00borsbors@rust-lang.org2025-09-28T21:40:04+00:00urn:sha1:f957826bff7a68b267ce75b1ea56352aed0cca0a
Re-enable assertions on macOS alt builds
These were previously disabled, in part for performance reasons, in part due to needing availability symbols `__isPlatformVersionAtLeast` and `__isOSVersionAtLeast` that `compiler-builtins` did not provide, see https://github.com/rust-lang/rust/pull/62592#issuecomment-510670657 and https://github.com/rust-lang/rust/pull/134275#issuecomment-2543067830 for failed checks.
Since https://github.com/rust-lang/rust/pull/138944 though, `std` now provides these symbols, so we should be able to re-enable LLVM assertions, debug assertions and overflow checks.
Fixes https://github.com/rust-lang/rust/issues/59637.
try-job: `*apple*`
Re-enable assertions on macOS2025-09-27T16:06:00+00:00Mads Marquartmads@marquart.dk2025-09-13T15:20:34+00:00urn:sha1:9878be7787a6239b9651eeaccb040778051038f6Rename `rust.use-lld` to `rust.bootstrap-override-lld`2025-09-26T18:21:21+00:00Jakub Beránekberykubik@gmail.com2025-09-25T20:45:07+00:00urn:sha1:852aa20c90cca64426516f46c3d89cfd57086ae8