Skip to content

[beta] backports#154725

Merged
rust-bors[bot] merged 11 commits intorust-lang:betafrom
cuviper:beta-next
Apr 3, 2026
Merged

[beta] backports#154725
rust-bors[bot] merged 11 commits intorust-lang:betafrom
cuviper:beta-next

Conversation

@cuviper
Copy link
Copy Markdown
Member

@cuviper cuviper commented Apr 2, 2026 •
edited by rustbot
Loading

r? cuviper

folkertdev and others added 11 commits April 2, 2026 10:41
@folkertdev @cuviper
aarch64: fix UB in non-power-of-two reads and writes
e427d29 
(cherry picked from commit 2fa37e7)
@folkertdev @cuviper
add neon load/store assembly test
73caca4 
(cherry picked from commit 35f9cb6)
@dianne @cuviper
don't drop arguments' temporaries in dbg!
4f50466 
(cherry picked from commit 51816ef)
@dianne @cuviper
update diagnostic for variables moved by dbg!
1374038 
(cherry picked from commit 7d1b41c)
@mu001999 @cuviper
Init self_decl with a correct vis
195f976 
(cherry picked from commit 01795c3)
@dianqk @cuviper
Update LLVM to 22.1.2
6db4dfe 
(cherry picked from commit 283d705)
@nikic @cuviper
[perf] Revert FastISel patch
533179a 
This change caused a significant compile-time regression for
debug builds.

(cherry picked from commit 1a32061)
@tgross35 @cuviper
core: Destabilize beta-stable RangeInclusiveIter::remainder
b7bdc7a 
As discussed, make this portion of the range API unstable again. This
will now be tracked under `new_range_remainder`.

Discussion: https://rust-lang.zulipchat.com/#narrow/channel/327149-t-libs-api.2Fapi-changes/topic/.60RangeFrom.3A.3Aremainder.60.20possible.20panic/with/582108913
(cherry picked from commit cbc9434)
@tgross35 @cuviper
core: Move {RangeIter, RangeFromIter}::remainder to `new_range_rema…
f68f598 
…inder`

Split the remainder functions from the rest of `std::range`.

(cherry picked from commit 0bb3fe3)
@wesleywiser @cuviper
Revert "Fix: On wasm targets, call panic_in_cleanup if panic occurs…
5dacf5d 
… in cleanup"

This reverts commit acbfd79.

(cherry picked from commit c9d3a00)
@tgross35 @cuviper
core: Update the feature gate on TryFrom<integer> for bool
940fc4d 
This implementation was added recently in f12288e
("TryFrom<integer> for bool") but used an old feature gate and
stabilization version. Update to reflect when these were actually added.

(cherry picked from commit 02b516a)
@rustbot rustbot added A-compiletest Area: The compiletest test runner A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) 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. labels Apr 2, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Apr 2, 2026

⚠️ Warning ⚠️

@cuviper
Copy link
Copy Markdown
Member Author

cuviper commented Apr 2, 2026

@folkertdev -- I found that your fix to deinterleaving_load! backported cleanly, but interleaving_store! doesn't exist on beta (without rust-lang/stdarch#2032). The new test still passes, but let me know if we need a fix somewhere in the older code too.

@cuviper
Copy link
Copy Markdown
Member Author

cuviper commented Apr 2, 2026

@bors r+ rollup=never

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 2, 2026

📌 Commit 940fc4d has been approved by cuviper

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 Apr 2, 2026
@folkertdev
Copy link
Copy Markdown
Contributor

folkertdev commented Apr 3, 2026

@folkertdev -- I found that your fix to deinterleaving_load! backported cleanly, but interleaving_store! doesn't exist on beta (without rust-lang/stdarch#2032). The new test still passes, but let me know if we need a fix somewhere in the older code too.

That's expected, the interleaving_store! macro is only added in a later commit, so beta still uses the earlier manual implementation (which is correct because it does not use ptr::read_unaligned but instead uses an LLVM intrinsic).

@rust-bors

This comment has been minimized.

Sign in to view
rust-bors bot pushed a commit that referenced this pull request Apr 3, 2026
@bors
Auto merge of #154725 - cuviper:beta-next, r=cuviper
94d9a11 
[beta] backports

- stdarch subtree update #153336 (partial)
  - aarch64: fix UB in non-power-of-two reads and writes rust-lang/stdarch#2042
- add neon load/store assembly test #154094
- don't drop arguments' temporaries in `dbg!` #154074
- Init self_decl with a correct vis #154313
- Update LLVM to 22.1.2 #154344
- [perf] Revert FastISel patch #154511
- core: Destabilize beta-stable `RangeInclusiveIter::remainder` #154459
- Revert "Fix: On wasm targets, call `panic_in_cleanup` if panic occurs in cleanup" #154700
- core: Update the feature gate on `TryFrom<integer> for bool` #154691

r? cuviper
@Zalathar
Copy link
Copy Markdown
Member

Zalathar commented Apr 3, 2026

At 3 hours into the run, the dist-x86_64-linux job still hasn't been picked up by a runner:

Evaluating job.if
Evaluating: success()
Result: true
Requested labels: codebuild-ubuntu-22-36c-23928791480-1
Job defined at: rust-lang/rust/.github/workflows/ci.yml@refs/heads/automation/bors/auto
Waiting for a runner to pick up this job...

@bors cancel

@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 3, 2026

Auto build was cancelled. Cancelled workflows:

The next pull request likely to be tested is #154740.

@Zalathar
Copy link
Copy Markdown
Member

Zalathar commented Apr 3, 2026

Scheduling: Make sure this gets another chance before the next rollup.

@bors p=5

@rust-bors

This comment has been minimized.

Sign in to view
@rust-bors rust-bors bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Apr 3, 2026
@rust-bors
Copy link
Copy Markdown
Contributor

rust-bors bot commented Apr 3, 2026

☀️ Test successful - CI
Approved by: cuviper
Duration: 3h 10m 39s
Pushing cc969f3 to beta...

@rust-bors rust-bors bot merged commit cc969f3 into rust-lang:beta Apr 3, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Apr 3, 2026
@cuviper cuviper mentioned this pull request Apr 4, 2026
Closed
@theemathas theemathas mentioned this pull request Apr 8, 2026
Open
@cuviper cuviper mentioned this pull request Apr 8, 2026
Merged
rust-bors bot pushed a commit that referenced this pull request Apr 9, 2026
@bors
Auto merge of #154999 - cuviper:beta-next, r=cuviper
2eccf47 
[beta] reverts and backports

This reverts two `dbg!` changes to avoid regressions[^1][^2] in the upcoming 1.95 release:

- std: avoid tearing `dbg!` prints #149869
- don't drop arguments' temporaries in `dbg!` #154074
  - ... which was previously backported in #154725

This also reverts a stabilization over a late issue[^3] of semantics:

- Stabilize `assert_matches` #137487

And a few other backport/reverts from `main`:

- Revert performing basic const checks in typeck on stable #154930 / #155033
- Revert "`-Znext-solver` Remove the forced ambiguity hack from search graph" #154712
- Clarify that core::range ranges do not have special syntax #155002
  
[^1]: #153850
[^2]: #154988
[^3]: #154406
rust-bors bot pushed a commit that referenced this pull request Apr 9, 2026
@bors
Auto merge of #154999 - cuviper:beta-next, r=cuviper
2c8c85d 
[beta] reverts and backports

This reverts two `dbg!` changes to avoid regressions[^1][^2] in the upcoming 1.95 release:

- std: avoid tearing `dbg!` prints #149869
- don't drop arguments' temporaries in `dbg!` #154074
  - ... which was previously backported in #154725

This also reverts a stabilization over a late issue[^3] of semantics:

- Stabilize `assert_matches` #137487

And a few other backport/reverts from `main`:

- Revert performing basic const checks in typeck on stable #154930 / #155033
- Revert "`-Znext-solver` Remove the forced ambiguity hack from search graph" #154712
- Clarify that core::range ranges do not have special syntax #155002

Clippy is backporting 2 ICE fixes and 1 perf regression (via #155051):

- rust-lang/rust-clippy#16685 already backported in #154211 to stable. This makes sure that it doesn't regress again in beta/next stable
- rust-lang/rust-clippy#16659 The ICE that is being fixed here was introduced in the 1.95 release cycle
- rust-lang/rust-clippy#16652 Perf regression introduced in the 1.95 release cycle.
  
[^1]: #153850
[^2]: #154988
[^3]: #154406
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@cuviper cuviper

Labels

A-compiletest Area: The compiletest test runner A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) 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.

Projects

None yet

Milestone

1.95.0

Development

Successfully merging this pull request may close these issues.

10 participants

@cuviper @rustbot @folkertdev @Zalathar @dianne @mu001999 @dianqk @nikic @tgross35 @wesleywiser