-
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
More linting tweaks #105416
More linting tweaks #105416
Conversation
Because it's always `'tcx`.
Because it makes more sense that way.
These each have a single call site, due to being called from a "combined" lint pass.
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit d049be3 with merge 858ff1cdb6da6c41638d404e35a962f37e2fc512... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (858ff1cdb6da6c41638d404e35a962f37e2fc512): comparison URL. Overall result: ❌ regressions - no 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. @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.
CyclesThis benchmark run did not return any relevant results for this metric. |
@bors r+ |
Disappoining perf results, I saw improvements locally. I guess with PGO/BOLT the version compiled on CI was already inlining those functions. Though they may still help platforms that aren't built with PGO/BOLT. |
⌛ Testing commit d049be3 with merge 85868c6419b82d9c77d6f17ddd82339a2827a375... |
💔 Test failed - checks-actions |
Seems to be a network error, the failing log ends with several repetitions of this:
@bors retry |
⌛ Testing commit d049be3 with merge 910b4af6a0a20dcd18974e9196a195f8daf5ecd6... |
💔 Test failed - checks-actions |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
☀️ Test successful - checks-actions |
Finished benchmarking commit (c6fcdb6): comparison URL. Overall result: ❌ regressions - no action needed@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.
CyclesThis benchmark run did not return any relevant results for this metric. |
…s, r=cjgillot Fix lint perf regressions rust-lang#104863 caused small but widespread regressions in lint performance. I tried to improve things in rust-lang#105291 and rust-lang#105416 with minimal success, before fully understanding what caused the regression. This PR effectively reverts all of rust-lang#105291 and part of rust-lang#104863 to fix the perf regression. r? `@cjgillot`
…jgillot More linting tweaks Squeeze a little more blood from this stone. r? `@cjgillot`
Squeeze a little more blood from this stone.
r? @cjgillot