-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Cleanup in the attribute parsers #149789
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
base: main
Are you sure you want to change the base?
Cleanup in the attribute parsers #149789
Conversation
|
Some changes occurred in compiler/rustc_attr_parsing |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Cleanup in the attribute parsers
This comment has been minimized.
This comment has been minimized.
|
Doubt it but we can try |
|
@bors r+ rollup was debating whether to cancel the perf run. I guess we can either rollup never and get the perf run later or keep the run going. If we keep the current one going then this pr can be part of the next roll-up and will use fewer ci resources and land quicker so I'm letting the perf run here continue and am explicitly rolling the pr up. |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (c626dd2): comparison URL. Overall result: ❌✅ regressions and improvements - no action neededBenchmarking 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. @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.4%, secondary 0.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 473.701s -> 470.928s (-0.59%) |
|
Nothing it seems |
|
Agreed this is probably just noise, I don't think this needs to be rollup=never |
PathParser, because we statically know which variant we're inr? @jdonszelmann