Rollup of 11 pull requests by JonathanBrouwer · Pull Request #162139 · rust-lang/rust

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

JonathanBrouwer · 2026-09-01T17:49:55Z

Successful merges:

rustdoc: add --print option #151618 (rustdoc: add --print option)
Update icu_list dependency to 2.3 #161287 (Update icu_list dependency to 2.3)
change DEFAULT_STACK_SIZE to be 32MB on s390x #161767 (change DEFAULT_STACK_SIZE to be 32MB on s390x)
Diverse offload fixes #161968 (Diverse offload fixes)
Remove -Zsaturating-float-casts flag #161971 (Remove -Zsaturating-float-casts flag)
Rework next_power_of_two to always be 1 << … #161209 (Rework next_power_of_two to always be 1 << …)
Move more rustdoc-html tests using --test into the right folder #162014 (Move more rustdoc-html tests using --test into the right folder)
Change some Infallible to ! in std #162073 (Change some Infallible to ! in std)
Remove gate_check from AttributeStability::Unstable #162086 (Remove gate_check from AttributeStability::Unstable)
alloc crate: shrink undocumented unsafe blocks #162102 (alloc crate: shrink undocumented unsafe blocks)
make it clear that Range cannot represent arbitrary ranges #162110 (make it clear that Range cannot represent arbitrary ranges)

r? @ghost

Create a similar rollup

I added this flag back in 2017 to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

@rustbot

rustdoc: add `--print` option Context: `--print crate-root-lint-levels` (rust-lang#139180) is only available for `rustc` and `clippy-driver`, while it would make sense for it to also be available for `rustdoc` (à la rust-lang#83895.) Not too sure about the stability of `rustdoc --print=any` or if this needs a MCP; strictly speaking, only `rustdoc +nightly -Z unstable-options --print=crate-root-lint-levels` would be required (and the `rustdoc --print` would be stabilized together with `crate-root-lint-levels`), but I guess that makes sense to have all the `--print`s for consistency. For regression tests, not sure if ui or run-make is preferable, as run-make would need some sort of trait to avoid duplicating code between `rustc()` and `rustdoc()` (or just test `rustdoc` as it delegates to `rustc`): https://github.com/rust-lang/rust/blob/021fc25b7a48f6051bee1e1f06c7a277e4de1cc9/tests/run-make/print-crate-root-lint-levels/rmake.rs#L82-L88 @rustbot label +A-CLI +A-print-requests

Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

…isDenton change DEFAULT_STACK_SIZE to be 32MB on s390x `tests/ui/match/match-stack-overflow-72933-.rs` crashes on s390x due to hitting stack_size limit(rust-lang#161742). changing the size to 32MB on s390x fixes the crash.

@ZuseZ4

Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

…RalfJung Remove -Zsaturating-float-casts flag I added this flag back in 2017 (rust-lang#45205) to enable benchmarking of the saturating semantics when it was newly implemented and still experimental. But saturation has been the official semantics for float<->int `as` casts for years now. A flag for turning it off no longer serves any purpose, it's just `-Zplease-miscompile-casts` now.

@clarfonthey

Rework `next_power_of_two` to always be `1 << …` r? @clarfonthey Who accidentally nerd-sniped me by mentioning rust-lang#161069 This obviates that PR by reworking the `(checked_)next_power_of_two` logic to calculate the necessary exponent e, then return 2ᵉ, so it's structurally obvious from the IR -- the `shl nuw 1, …` instruction -- that it's always a power of two. As always, the reason this is tricky is because shifts don't work for `<< Self::BITS`. The previous code handled that by checking `self <= 1` first, and thus doing a `-1 >> n` where `n < BITS`. This code instead flips the check: it looks up-front for a value that will wrap (an input above `1 << (BITS - 1)`) and thus by excluding those cases the calculated `1 << n` always has `n < BITS`. And the codegen tests show that, without needing any `llvm.assume`s, LLVM can take advantage of it to do things like rewriting `%` to masking. Plus the overflow check optimizes out for constrained inputs like slice lengths.

@fmease

…ease Move more `rustdoc-html` tests using `--test` into the right folder Follow-up of rust-lang#161944. I double-checked if more `rustdoc-html` tests were in the wrong folder and... yeah. So fixing that too. I'll send a patch to prevent that in the future (in `compiletest` I guess, doesn't seem like a `tidy` thing). Oh also second commit is me realizing that some ui tests were using `compile-args` (which doesn't exist anymore) and without `@`. Anyway, fixed that too. r? @fmease

…nthey Change some `Infallible` to `!` in std I believe this desirable since we recommend `!` over `Infallible`, so std follows its own advice. Most changes are to unstable features, but not all. Similar changes in compiler have to wait for a bootstrap update.

@mejrs

… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

…oc, r=clarfonthey `alloc` crate: shrink undocumented `unsafe` blocks Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

make it clear that Range cannot represent arbitrary ranges This seems like a useful clarification, though it is already heavily implied by the first sentence in the docs. What is less clear to me is what type one *should* use to represent arbitrary ranges. Should we recommend `(Bound<T>, Bound<T>)` for that purpose? It seems best-stuied, and is already used for that purpose by the btree collections and in rust-lang#136903. However, I suspect it is also common that one wants to represent an arbitrary range that's bounded on both sides. `RangeInclusive` can represent all those (though representing the empty range is a bit awkward), `Range` cannot. Nominating for t-libs to get their general vibe on what we want to recommend here, if anything.

JonathanBrouwer · 2026-09-01T17:50:24Z

@bors r+ p=5

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,x86_64-gnu-aux,x86_64-gnu-llvm-21-3,x86_64-msvc-1,aarch64-apple-1,aarch64-apple-2,x86_64-mingw-1,i686-msvc-1,i686-msvc-2

rust-bors · 2026-09-01T17:50:28Z

📌 Commit 31ea8db has been approved by JonathanBrouwer

It is now in the queue for this repository.

Rollup of 11 pull requests try-job: dist-various-1 try-job: test-various try-job: x86_64-gnu-aux try-job: x86_64-gnu-llvm-21-3 try-job: x86_64-msvc-1 try-job: aarch64-apple-1 try-job: aarch64-apple-2 try-job: x86_64-mingw-1 try-job: i686-msvc-1 try-job: i686-msvc-2

rust-log-analyzer · 2026-09-01T19:24:04Z

The job aarch64-apple-1 failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

Saved the actual stdout to `/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option/sanitizer-option.stdout`
normalized stdout:
running 1 test
test $DIR/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
The actual stdout differed from the expected stdout
To update references, rerun the tests and pass the `--bless` flag
To only update this specific test, also pass `--test-args doctest/sanitizer-option.rs`
error: 1 errors occurred comparing output.
status: exit status: 0
command: env -u RUSTC_LOG_COLOR RUSTC_ICE="0" RUST_BACKTRACE="short" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2/bin/rustdoc" "/Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs" "-Zsimulate-remapped-rust-src-base=/rustc/FAKE_PREFIX" "-Ztranslate-remapped-path-to-local-path=no" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/.cargo" "-Z" "ignore-directory-in-diagnostics-source-blocks=/Users/runner/work/rust/rust/vendor" "--sysroot" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/stage2" "--target=aarch64-apple-darwin" "--check-cfg" "cfg(test,FALSE)" "--error-format" "json" "--json" "future-incompat" "-Ccodegen-units=1" "-Zui-testing" "-Zdeduplicate-diagnostics=no" "-Zwrite-long-types-to-disk=no" "-Cstrip=debuginfo" "-o" "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/test/rustdoc-ui/doctest/sanitizer-option" "-Znext-solver=coherence" "-A" "internal_features" "-A" "incomplete_features" "-A" "unused_parens" "-A" "unused_braces" "-Cdebuginfo=0" "--test" "-Z" "sanitizer=address" "-C" "unsafe-allow-abi-mismatch=sanitizer"
--- stdout -------------------------------
running 1 test
test /Users/runner/work/rust/rust/tests/rustdoc-ui/doctest/sanitizer-option.rs - z_flag_is_passed_to_rustc (line 11) ... ok

rust-bors · 2026-09-01T19:25:51Z

PR #162014, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

rust-bors · 2026-09-01T20:25:27Z

💔 Test for 6a3484a failed: CI. Failed jobs:

try - aarch64-apple-1 (web logs, enhanced plaintext logs)
try - i686-msvc-1 (web logs, enhanced plaintext logs)
try - x86_64-mingw-1 (web logs, enhanced plaintext logs)
try - x86_64-msvc-1 (web logs, enhanced plaintext logs)

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

hanna-kruppeand others added 30 commits August 29, 2026 13:50

doc: PrintKind
938b233

rustdoc: cleanup main_args() markdown handling
2e7e5cb

Move more rustdoc-html tests using --test into the right folder
41258df

Fix invalid compile-args ui tests argument
614d9ea

rustdoc: add --print option
57cc38f

rustdoc: test --print option
736a14b

rustdoc: filter print kinds
0e6616b

change DEFAULT_STACK_SIZE to be 17MB
d3a3f13
tests/ui/match/match-stack-overflow-72933-.rs crashes on s390x due to hitting stack_size limit. changing the size to 17MB the crash.

Rework next_power_of_two to always be 1 << …
f771946

alloc crate: shrink undocumented unsafe blocks
b5e8344
Reduce the scope of `unsafe` blocks that are not yet documented by moving safe operations out of the blocks, making it easier to add the missing documentation in the future.

Some fixes re linking and no-std
ac1ba50

Move run-make tests to offload folder
5698c8d

Update icu_list to 2.3
80dc5df

rustdoc: add tests for Markdown files
bf27a5a

Dogfood never type in std
dd13221

Normalize more rustdoc-ui doctest output
5ba810f

make it clear that Range cannot represent arbitrary ranges
baf382f

Remove gate_check from AttributeStability::Unstable
7a02fd9

Rollup merge ofrust-lang#161287- robertbastian:23, r=Manishearth
3079b23
Update `icu_list` dependency to 2.3 This removes the `icu_collections` transitive dependency, and uses the smaller `icu_locale_fallback` instead of `icu_locale`. r? manishearth

Rollup merge ofrust-lang#161968- Sa4dUs:offload-fix, r=ZuseZ4
1c83ec2
Diverse offload fixes `HostMetadata` pass skips linking. Now, `offload_kernel` macro lowers to `core` instead of `std`. closes: rust-lang#161703 r? @ZuseZ4

Rollup merge ofrust-lang#162086- JonathanBrouwer:remove_gate_check,…
bf5e0dc
… r=mejrs Remove `gate_check` from `AttributeStability::Unstable` Based on the idea from rust-lang#162051 (comment) r? @mejrs

rust-borsBot added the rollup A PR which is a rollup label Sep 1, 2026

rust-borsBot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 1, 2026

This comment has been minimized.
Sign in to view

JonathanBrouwer mentioned this pull request Sep 1, 2026
Move more rustdoc-html tests using --test into the right folder #162014
Open

rust-borsBot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Sep 1, 2026

JonathanBrouwer closed this Sep 1, 2026

rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

rust-borsBot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Sep 1, 2026

Uh oh!

Uh oh!

Conversation

JonathanBrouwer commented Sep 1, 2026

Uh oh!

JonathanBrouwer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

This comment has been minimized.

rust-log-analyzer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants

Uh oh!

Uh oh!

Conversation

JonathanBrouwer commented Sep 1, 2026

Uh oh!

JonathanBrouwer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

This comment has been minimized.

rust-log-analyzer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants

Uh oh!

Uh oh!

Conversation

JonathanBrouwer commented Sep 1, 2026

Uh oh!

JonathanBrouwer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

This comment has been minimized.

rust-log-analyzer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants

Uh oh!

Uh oh!

Conversation

JonathanBrouwer commented Sep 1, 2026

Uh oh!

JonathanBrouwer commented Sep 1, 2026

Uh oh!

rust-borsBot commented Sep 1, 2026