-
Notifications
You must be signed in to change notification settings - Fork 13.9k
Mark desugared range expression spans with DesugaringKind::RangeExpr #146069
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
Conversation
|
r? @SparrowLii rustbot has assigned @SparrowLii. Use |
|
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
b4bfa81 to
ac6978f
Compare
ac6978f to
7dce8b2
Compare
This comment has been minimized.
This comment has been minimized.
|
@SparrowLii are you able to review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the late reviewing. The impl looks good to me. I'd like to run a perf test. We can merge it if there's no regression
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Mark desugared range expression spans with DesugaringKind::RangeExpr
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (b4fcc0d): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.2%, secondary 6.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 468.849s -> 470.946s (0.45%) |
|
Just a guess but let's see if that fixes it. |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Mark desugared range expression spans with DesugaringKind::RangeExpr
|
Those results are worse so I took that commit back. I'm not finding anything actionable in cachegrind. I think this is a mixture of some noise and some inevitable loss with creating more span contexts. |
0cf87a7 to
7911460
Compare
This comment has been minimized.
This comment has been minimized.
7dce8b2 to
b8af04c
Compare
This comment has been minimized.
This comment has been minimized.
|
We focus on the primary cases so I think the second impl and results are a bit better. Collecting lang items in HIR is very valuable so the regression doesn't block this PR IMO. Just seeing if there are some optimiztions. Anyway I think we can merge it next week. |
|
@camsteffen Could you re-push the commit which generates the soecend perf resutlts? Then I can give a r+ |
The need for this arose when encountering range expressions surrounded by parenthesis, where we want the span desugaring mark to be preserved.
b8af04c to
6d61dad
Compare
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
|
Ok, I squashed it in. Sorry for the delay, I think I misunderstood your comment before. |
|
@bors r+ rollup=never |
|
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing b1b464d (parent) -> 23fced0 (this PR) Test differencesShow 26 test diffs26 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 23fced0fcc5e0ec260d25f04a8b78b269e5e90f0 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (23fced0): comparison URL. Overall result: ❌ regressions - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.5%, secondary 4.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 1.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 0.1%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 474.573s -> 475.144s (0.12%) |
|
perf triage: Regression was deemed acceptable here: #146069 (comment) Note that the regression mostly affects very short benchmarks (incr-unchanged and such), so this is not as bad as it might seem from the summary. @rustbot label: +perf-regression-triaged |
…rrowLii Mark desugared range expression spans with DesugaringKind::RangeExpr This is a prerequisite to removing `QPath::LangItem` (rust-lang#115178) because otherwise there would be no way to detect a range expression in the HIR. There are some non-obvious Clippy changes so a Clippy team review would be good.
This is a prerequisite to removing
QPath::LangItem(#115178) because otherwise there would be no way to detect a range expression in the HIR.There are some non-obvious Clippy changes so a Clippy team review would be good.