Skip to content

Rollup of 15 pull requests - #163175

Closed
JonathanBrouwer wants to merge 43 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-e4GWzm6
Closed

JonathanBrouwer wants to merge 43 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-e4GWzm6

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Member

Successful merges:

Warning

This rollup conflicts with pending auto build #163165 and may need to be recreated if the pending build succeeds.

r? @ghost

Create a similar rollup

edwloef and others added 30 commits August 3, 2026 15:05
This appears to have become unused in August 2025. I noticed today
because of trying to consolidate versions of things in the toolchain.
simplify liveness sources to not need a lifetime or a location map
- tiny renamings
- tiny type simplifications (type ascription, closure return type)
- fixing a comment
and group it with related code
Add target-specific revisions to the `f16b` codegen test to account for
LoongArch and RISC-V lowering `f16b` to LLVM `half` rather than `bfloat`.
Update deprecated rustc_hir imports

Followup to rust-lang#160336

That's ~half of them, I'm not doing it all in one go to reduce conflicts.
Detect missing else in let statement

Fixes rust-lang#135857

I add the help message in rustc_resolve. It now will display something like this:
```rust
error: expected identifier, found keyword `return`
 --> ./test.rs:8:24
  |
8 |      let Some(a) = bar{return;};
  |                    --- ^^^^^^ expected identifier, found keyword
  |                    |
  |                    while parsing this struct
  |
help: escape `return` to use it as an identifier
  |
8 |      let Some(a) = bar{r#return;};
  |                        ++

error[E0574]: expected struct, variant or union type, found local variable `bar`
 --> ./test.rs:8:20
  |
8 |      let Some(a) = bar{return;};
  |                    ^^^ not a struct, variant or union type
  |
help: try adding `else` here:
  |
8 |      let Some(a) = bar else {return;};
  |                        ++++

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0574`.
```
r? estebank
…kertdev

OpenBSD/sparc64 has switched from GCC to Clang
…=oli-obk

Skip redundant storage-conflict updates during coroutine layout

## Summary

When computing coroutine storage conflicts, we currently record conflicts between every pair in the live set. This PR instead remembers the last live set whose conflicts were recorded; if the current set is a subset, we skip the matrix updates. For example, after recording `{a, b, c}`, observing `{a, b}` adds no new conflicts.

I used an LLM to profile this change, and saw a compiler CPU reduction in the following projects:

- Codex: 2.69%
- Ruff: 2.84%
- uv: 5.28%
- ty: 3.28%
librustdoc: remove stale dep on base64

This appears to have become unused in August 2025. I noticed today because of trying to consolidate versions of things in the toolchain.
tests: Update `f16b` codegen test for LoongArch and RISC-V

Fixes rust-lang#163145
…-obk

treat inductive cycles as ambig

We needed inductive cycles to be `NoSolution` for proper `ParamEnv` normalization. With rust-lang#158643 this is no longer necessary, so lets make the stabilization of the new solver as small as possible.

r? types
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Sep 22, 2026
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver) labels Sep 22, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5

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

@rust-bors

rust-bors Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 37c2f01 has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot 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 22, 2026
@rust-bors

rust-bors Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

⌛ Trying commit 37c2f01 with merge d1cf565

To cancel the try build, run the command @bors try cancel.

Workflow: https://github.com/rust-lang/rust/actions/runs/35775101058

rust-bors Bot pushed a commit that referenced this pull request Sep 22, 2026
Rollup of 15 pull requests


try-job: dist-various-1
try-job: test-various
try-job: test-x86_64-gnu-aux
try-job: test-x86_64-gnu-llvm-21-3
try-job: test-x86_64-msvc-1
try-job: test-aarch64-apple-1
try-job: test-aarch64-apple-2
try-job: test-x86_64-mingw-1
try-job: test-i686-msvc
try-job: test-armhf-gnu
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-x86_64-gnu-llvm-21-3 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
test [crashes] tests/crashes/155761-1.rs ... ok
test [crashes] tests/crashes/158243.rs ... ok
test [crashes] tests/crashes/160329.rs ... ok
test [crashes] tests/crashes/158797.rs ... ok
2026-09-22T20:07:02.193487Z ERROR compiletest::runtest: fatal error, panic: "crashtest no longer crashes/triggers ICE, hooray! Please give it a meaningful name, add a doc-comment to the start of the test explaining why it exists and move it to tests/ui or wherever you see fit. Adding 'Fixes #<issueNr>' to your PR description ensures that the corresponding ticket is auto-closed upon merge. If you want to see verbose output, set `COMPILETEST_VERBOSE_CRASHES=1`."
test [crashes] tests/crashes/158773.rs ... ok
test [crashes] tests/crashes/160490.rs ... FAILED
test [crashes] tests/crashes/87577.rs ... ok
test [crashes] tests/crashes/88296.rs ... ok
test [crashes] tests/crashes/34127.rs ... ok
---

---- [crashes] tests/crashes/160490.rs stdout ----
------rustc stdout------------------------------

------rustc stderr------------------------------
error: unexpected `...`
##[error] --> /checkout/tests/crashes/160490.rs:2:6
  |
2 | fn f(...: u8) {}
  |      ^^^ not a valid pattern
  |
help: for a rest pattern, use `..` instead of `...`
---
  |      ^^^
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #145544 <https://github.com/rust-lang/rust/issues/145544>
  = note: `#[deny(varargs_without_pattern)]` (part of `#[deny(future_incompatible)]`) on by default
help: name the argument, or use `_` to continue ignoring it
  |
2 | fn f(_: ...: u8) {}
  |      ++

error[E0601]: `main` function not found in crate `160490`
##[error] --> /checkout/tests/crashes/160490.rs:2:17
  |
---
For more information about this error, try `rustc --explain E0601`.

------------------------------------------

error: crashtest no longer crashes/triggers ICE, hooray! Please give it a meaningful name, add a doc-comment to the start of the test explaining why it exists and move it to tests/ui or wherever you see fit. Adding 'Fixes #<issueNr>' to your PR description ensures that the corresponding ticket is auto-closed upon merge. If you want to see verbose output, set `COMPILETEST_VERBOSE_CRASHES=1`.

thread '[crashes] tests/crashes/160490.rs' panicked at src/tools/compiletest/src/runtest/crashes.rs:16:18:
fatal error
stack backtrace:
   5: __rustc::rust_begin_unwind

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

rust-bors Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

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

This rollup was thus unapproved.

@rust-bors rust-bors Bot removed the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Sep 22, 2026
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-aarch64-gnu-llvm-21-1 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
test [crashes] tests/crashes/157197.rs ... ok
test [crashes] tests/crashes/160329.rs ... ok
test [crashes] tests/crashes/158797.rs ... ok
test [crashes] tests/crashes/158773.rs ... ok
2026-09-22T20:18:15.339460Z ERROR compiletest::runtest: fatal error, panic: "crashtest no longer crashes/triggers ICE, hooray! Please give it a meaningful name, add a doc-comment to the start of the test explaining why it exists and move it to tests/ui or wherever you see fit. Adding 'Fixes #<issueNr>' to your PR description ensures that the corresponding ticket is auto-closed upon merge. If you want to see verbose output, set `COMPILETEST_VERBOSE_CRASHES=1`."
test [crashes] tests/crashes/160490.rs ... FAILED
test [crashes] tests/crashes/88296.rs ... ok
test [crashes] tests/crashes/87577.rs ... ok
test [crashes] tests/crashes/34127.rs ... ok
test [crashes] tests/crashes/54888.rs ... ok
---

---- [crashes] tests/crashes/160490.rs stdout ----
------rustc stdout------------------------------

------rustc stderr------------------------------
error: unexpected `...`
##[error] --> /checkout/tests/crashes/160490.rs:2:6
  |
2 | fn f(...: u8) {}
  |      ^^^ not a valid pattern
  |
help: for a rest pattern, use `..` instead of `...`
---
  |      ^^^
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #145544 <https://github.com/rust-lang/rust/issues/145544>
  = note: `#[deny(varargs_without_pattern)]` (part of `#[deny(future_incompatible)]`) on by default
help: name the argument, or use `_` to continue ignoring it
  |
2 | fn f(_: ...: u8) {}
  |      ++

error[E0601]: `main` function not found in crate `160490`
##[error] --> /checkout/tests/crashes/160490.rs:2:17
  |
---
For more information about this error, try `rustc --explain E0601`.

------------------------------------------

error: crashtest no longer crashes/triggers ICE, hooray! Please give it a meaningful name, add a doc-comment to the start of the test explaining why it exists and move it to tests/ui or wherever you see fit. Adding 'Fixes #<issueNr>' to your PR description ensures that the corresponding ticket is auto-closed upon merge. If you want to see verbose output, set `COMPILETEST_VERBOSE_CRASHES=1`.

thread '[crashes] tests/crashes/160490.rs' panicked at src/tools/compiletest/src/runtest/crashes.rs:16:18:
fatal error
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---- [crashes] tests/crashes/160490.rs stdout end ----

@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors try cancel

@rustbot 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 22, 2026
@rust-bors

rust-bors Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Try build cancelled. Cancelled workflows:

Hint: if you want to run another try build, you do not need to manually cancel the previous one. Just run @bors try and bors will cancel the previous build automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. rollup A PR which is a rollup T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)

Projects

None yet

Development

Successfully merging this pull request may close these issues.