Uh oh!
There was an error while loading. Please reload this page.
Remove NtExpr and NtLiteral - #138478
Conversation
This comment has been minimized.
This comment has been minimized.
1b55759 to
7f6b06cComparerustbot
commented
Mar 24, 2025
Could not assign reviewer from: |
nnethercote
commented
Mar 24, 2025
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
bors
commented
Mar 24, 2025
…try> Remove `NtExpr` and `NtLiteral` The next part of rust-lang#124141. r? `@petrochenkov`
nnethercote
commented
Mar 24, 2025
@rustbot ready |
bors
commented
Mar 24, 2025
☀️ Try build successful - checks-actions |
rust-timer
commented
Mar 24, 2025
Finished benchmarking commit (2f5db75): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking 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 the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary 1.6%, secondary -4.3%)This 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.
CyclesResults (primary 1.7%, secondary 8.5%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: missing data |
nnethercote
commented
Mar 25, 2025
The perf regressions have been seen previously in #124141, with the @rustbot label: +perf-regression-triaged |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
7f6b06c to
37af248Comparennethercote
commented
Mar 26, 2025
Thanks for the review. I have added two new commits addressing the comments. @rustbot ready |
bors
commented
Apr 1, 2025
☔ The latest upstream changes (presumably #138740) made this pull request unmergeable. Please resolve the merge conflicts. |
Notes about tests: - tests/ui/rfcs/rfc-2294-if-let-guard/feature-gate.rs: some messages are now duplicated due to repeated parsing. - tests/ui/rfcs/rfc-2497-if-let-chains/disallowed-positions.rs: ditto. - `tests/ui/proc-macro/macro-rules-derive-cfg.rs`: the diff looks large but the only difference is the insertion of a single invisible-delimited group around a metavar. - `tests/ui/attributes/nonterminal-expansion.rs`: a slight span degradation, somehow related to the recent massive attr parsing rewrite (rust-lang#135726). I couldn't work out exactly what is going wrong, but I don't think it's worth holding things up for a single slightly suboptimal error message.
In favour of the similar method on `Parser`, which works on things other than identifiers and lifetimes.
This makes the expression re-parsing more like how it's originally done in `parse_nonterminal`.
59f6ba4 to
592d113Comparennethercote
commented
Apr 1, 2025
I rebased. @bors r=petrochenkov |
bors
commented
Apr 1, 2025
bors
commented
Apr 2, 2025
bors
commented
Apr 2, 2025
☀️ 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 9b7d5ac (parent) -> 70dab5a (this PR) Test differencesShow 6 test diffsStage 1
Stage 2
Additionally, 2 doctest diffs were found. These are ignored, as they are noisy. Job group index
Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
rust-timer
commented
Apr 2, 2025
Finished benchmarking commit (70dab5a): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary 1.0%, secondary 0.1%)This 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.
CyclesResults (primary 1.6%, secondary 14.8%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 774.901s -> 774.398s (-0.06%) |
nnethercote
commented
Apr 2, 2025
Regressions were expected, alas. @rustbot label: +perf-regression-triaged |
The next part of #124141.
r? @petrochenkov