rust/compiler/rustc_middle, branch autohttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=auto2025-10-04T10:31:28+00:00Rollup merge of #147251 - jackh726:global-cache-non-concurrent-change, r=lcnr2025-10-04T10:31:28+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-10-04T10:31:28+00:00urn:sha1:684a872477146fb4c5eca0aadb90b1cd9e3f19ec
Do not assert that a change in global cache only happens when concurrent
Fixes rust-lang/trait-system-refactor-initiative#234
I think it should just be safe to remove this assert (rather than delaying a bug). If the previous and current result are the same, I wouldn't expect issues.
r? lcnr
Do not assert that a change in global cache only happens when concurrent2025-10-03T20:21:15+00:00jackh726git@jackhuey.me2025-10-02T00:51:44+00:00urn:sha1:55aeb1747d97b70c75220ade6cdc53523886defdAuto merge of #142771 - dianqk:mir-stmt-debuginfo, r=cjgillot2025-10-03T11:49:42+00:00borsbors@rust-lang.org2025-10-03T11:49:42+00:00urn:sha1:8b6b15b877fbceb1ee5d9a5a4746e7515901574a
Introduce debuginfo to statements in MIR
The PR introduces support for debug information within dead statements. Currently, only the reference statement is supported, which is sufficient to fix rust-lang/rust#128081.
I don't modify Stable MIR, as I don't think we need debug information when using it.
This PR represents the debug information for the dead reference statement via `#dbg_value`. For example, `let _foo_b = &foo.b` becomes `#dbg_value(ptr %foo, !22, !DIExpression(DW_OP_plus_uconst, 4, DW_OP_stack_value), !26)`. You can see this here: https://rust.godbolt.org/z/d43js6adv.
The general principle for handling debug information is to never provide less debug information than the optimized LLVM IR.
The current rules for dropping debug information in this PR are:
- If the LLVM IR cannot represent a reference address, it's replaced with poison or simply dropped. For example, see: https://rust.godbolt.org/z/shGqPec8W. I'm using poison in all such cases now.
- All debuginfos is dropped when merging multiple successor BBs. An example is available here: https://rust.godbolt.org/z/TE1q3Wq6M.
I doesn't drop debuginfos in `MatchBranchSimplification`, because LLVM also pick one branch for it.
Auto merge of #147138 - jackh726:split-canonical-bound, r=lcnr2025-10-02T08:09:33+00:00borsbors@rust-lang.org2025-10-02T08:09:33+00:00urn:sha1:4b9c62b4da3e17cee99d3d2052f1c576b188e2a8
Split Bound index into Canonical and Bound
See [#t-types/trait-system-refactor > perf `async-closures/post-mono-higher-ranked-hang.rs`](https://rust-lang.zulipchat.com/#narrow/channel/364551-t-types.2Ftrait-system-refactor/topic/perf.20.60async-closures.2Fpost-mono-higher-ranked-hang.2Ers.60/with/541535613) for context
Things compile and tests pass, but not sure if this actually solves the perf issue (edit: it does). Opening up this to do a perf (and maybe crater) run.
r? lcnr
mir-opt: Eliminate dead statements even if they are used by debuginfos2025-10-02T06:58:59+00:00dianqkdianqk@dianqk.net2025-07-19T10:49:47+00:00urn:sha1:8da04285cf6fe61587e16155a8b224dba64bf0bemir-opt: Eliminate trivial unnecessary storage annotations2025-10-02T06:55:51+00:00dianqkdianqk@dianqk.net2025-07-15T14:54:54+00:00urn:sha1:85b2f706939528b5796d98e82c183637f8338cd1simplifycfg: Preserve debuginfos when merging bbs2025-10-02T06:55:50+00:00dianqkdianqk@dianqk.net2025-07-10T13:20:54+00:00urn:sha1:cc93132ae4f5477297ecddb0c07d2e8c74075f0cmir-opt: Eliminate dead ref statements2025-10-02T06:55:50+00:00dianqkdianqk@dianqk.net2025-06-08T07:30:09+00:00urn:sha1:571412f8190089c36758031fe09fc0ece59be6b7Auto merge of #147055 - beepster4096:subtype_is_not_a_projection, r=lcnr2025-10-02T01:54:48+00:00borsbors@rust-lang.org2025-10-02T01:54:48+00:00urn:sha1:42b384ec0dfcd528d99a4db0a337d9188a9eecaa
Turn ProjectionElem::Subtype into CastKind::Subtype
I noticed that drop elaboration can't, in general, handle `ProjectionElem::SubType`. It creates a disjoint move path that overlaps with other move paths. (`Subslice` does too, and I'm working on a different PR to make that special case less fragile.) If its skipped and treated as the same move path as its parent then `MovePath.place` has multiple possible projections. (It would probably make sense to remove all `Subtype` projections for the canonical place but it doesn't make sense to have this special case for a problem that doesn't actually occur in real MIR.)
The only reason this doesn't break is that `Subtype` is always the sole projection of the local its applied to. For the same reason, it works fine as a `CastKind` so I figured that makes more sense than documenting and validating this hidden invariant.
cc rust-lang/rust#112651, rust-lang/rust#133258
r? Icnr (bc you've been the main person dealing with `Subtype` it looks like)
Split Bound into Canonical and Bound2025-09-30T16:58:28+00:00jackh726git@jackhuey.me2025-09-28T23:04:55+00:00urn:sha1:d1bbd39c59523d7a5499816a9da200a5910f8b7f