-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrap the whole LocalInfo in ClearCrossCrate. #108944
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 345a9749c71bab291a3ffb43e0194342ae11291a with merge a2523b11c11aa554813e8ecc01272e3bb92ba1d2... |
This comment was marked as outdated.
This comment was marked as outdated.
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
345a974
to
e487459
Compare
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
1 similar comment
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (d6008dafc64975183e3a82d2e5083652a5f4c404): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
Perf: ~0.8% improvement in instruction count, driven by reduced crate metadata encoding/decoding (crate_metadata -1.8%). r? compiler |
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
clippy tests also need some blessing. r? @oli-obk |
☀️ Test successful - checks-actions |
Finished benchmarking commit (511364e): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
Perf report : identical to #108944 (comment) |
A lot of movement in many metrics in those results. Cycles and wall-time look a little worse than instruction counts, like they are slight regressions overall. Results in secondary benchmarks are worse than primary benchmarks (which is better than the other way around). But binary size reductions are quite high on numerous benchmarks. I guess overall you could say all of this balances out. |
@rustbot label: +perf-regression-triaged |
Update the toolchain to use nightly-2023-04-16. Changes were related to the following changes to the toolchain: - rust-lang/rust#108944 - rust-lang/rust#108148 - rust-lang/rust#108471 - rust-lang/rust#109358 - rust-lang/rust#109849 - rust-lang/rust#109819 - rust-lang/rust#109718 - rust-lang/rust#109092 - rust-lang/rust#108856 - rust-lang/rust#105613 - rust-lang/rust#103042 - rust-lang/rust#109716 - rust-lang/rust#108340 - rust-lang/rust#102906 - rust-lang/rust#98112 - rust-lang/rust#108080
@cjgillot hi, it seems that this pr introduced some clippy false-positves of redundant_clone. namely, rust-lang/rust-clippy#10577 and rust-lang/rust-clippy#10517 (added testcases) and maybe this too: rust-lang/rust-clippy#10545 I concluded this bisect with this branch: https://github.com/rust-lang/rust/compare/master...ryoqun:rust:clippy-redundant-clone-false-positives?expand=1 and this command:
seems bunch of nightly clippy users are noticing likewise. so i think there will be more after 1.70 is released? (EDIT: i also checked latest nightly 2023-05-26 is still affected as well) |
This needs to be fixed on the clippy side. We must have been using the LocalInfo mistakenly in the clippy lint |
Move `redundant_clone` to `nursery` changelog: [`redundant_clone`]: Move to `nursery` A bunch of FPs in `redundant_clone` have sprung up after upstream MIR changes: rust-lang/rust#108944 - #10870 - #10577 - #10545 - #10517 r? `@flip1995`
MIR contains a lot of information about locals. The primary purpose of this information is the quality of borrowck diagnostics.
This PR aims to drop this information after MIR analyses are finished, ie. starting from post-cleanup runtime MIR.