-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
Always inline traversal skeletons #124260
base: master
Are you sure you want to change the base?
Conversation
These methods all just delegate to another part of the traversal machinery, but the compiler does not always select them for inlining which can give rise to missed optimisations.
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…=<try> Always inline traversal skeletons These methods all just delegate to another part of the traversal machinery, but the compiler does not always select them for inlining which can give rise to missed optimisations. Local perf on aarch64 shows mild/positive results, but obviously we should check on CI too. r? wg-compiler-performance
☀️ Try build successful - checks-actions |
Finished benchmarking commit (c2dfb80): 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)This benchmark run did not return any relevant results for this metric. 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 671.419s -> 670.006s (-0.21%) |
Hm, perf doesn't seem helped much. I'm not surprised -- these methods are small enough that I'd expect the compiler to know to inline them already? @rustbot author |
These methods all just delegate to another part of the traversal machinery, but the compiler does not always select them for inlining which can give rise to missed optimisations.
Local perf on aarch64 shows mild/positive results, but obviously we should check on CI too.
r? wg-compiler-performance