partially revertish lazily "compute" anon const default substs#92805
partially revertish lazily "compute" anon const default substs#92805bors merged 4 commits intorust-lang:masterfrom
lazily "compute" anon const default substs#92805Conversation
|
Some changes occured to the CTFE / Miri engine cc @rust-lang/miri Some changes occured to rustc_codegen_cranelift cc @bjorn3 Some changes occured to the CTFE / Miri engine cc @rust-lang/miri Some changes occurred in src/tools/clippy. cc @rust-lang/clippy |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Why is this getting reverted? |
|
I knew I forgot something when making this PR.... will add a description explaining the "why" 😅 |
|
I think we want I never got to filtering the generic params (which is also more difficult than originally assumed) and we will probably implement a different solution for the "unused substs" problem in the future, so keeping these changes doesn't seem too practical for And finally, we don't need any substs filtering for |
|
@bors r+ |
|
📌 Commit e24b05e122b134496aa76e6b2333b1cbb5b618af has been approved by |
|
@bors rollup=never this is perf sensitive |
|
Also some of these commit messages look like they should be fixed before merging.^^ |
1facfa2 to
1312f61
Compare
lazily "compute" anon const default substslazily "compute" anon const default substs
1312f61 to
7e2cf3b
Compare
9d2a60e to
6899064
Compare
|
@bors r+ rollup=never |
|
📌 Commit 6899064be3ddaee785686a614179d9ccfd0d66a8 has been approved by |
|
☔ The latest upstream changes (presumably #92883) made this pull request unmergeable. Please resolve the merge conflicts. |
6899064 to
3f3a10f
Compare
|
@bors r=lcnr rollup=never |
|
📌 Commit 3f3a10f has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (7be8693): comparison url. Summary: This change led to moderate relevant mixed results 🤷 in compiler performance.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression |
|
seems to mostly mirror the perf results from #87280 https://perf.rust-lang.org/compare.html?start=3b5df014390dcef66cc35f968fe51e9558e6ca13&end=22a1bd761de8b0ac85d9ecaae5f262d5798a4409 a bit surprised that the ctfe tests stayed about the same even though they regressed by about 4% in the original pr. it might make some sense to look a bit more into the impact of using `ty::Unevaluated' during type folding. Might get some more perf back in stress tests by adding some inlines there. |
partially revertish `lazily "compute" anon const default substs` reverts #87280 except for some of the changes around `ty::Unevaluated` having a visitor and a generic for promoted why revert: <rust-lang/rust#92805 (comment)> r? `@lcnr`
Needed to adjust stdout for trait_impls, due to new allocator generic parameter for `Vec` and `Box`, decided it wasn't worth a separate commit.
partially revertish `lazily "compute" anon const default substs` reverts #87280 except for some of the changes around `ty::Unevaluated` having a visitor and a generic for promoted why revert: <rust-lang/rust#92805 (comment)> r? `@lcnr`
partially revertish `lazily "compute" anon const default substs` reverts #87280 except for some of the changes around `ty::Unevaluated` having a visitor and a generic for promoted why revert: <rust-lang/rust#92805 (comment)> r? `@lcnr`
reverts #87280 except for some of the changes around
ty::Unevaluatedhaving a visitor and a generic for promotedwhy revert: #92805 (comment)
r? @lcnr