-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Prefer not to early return from derived visitables #124263
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
LLVM is not able to tail-call optimise the final early return, as there instructions that follow it. Making that call the returned expression resolves this.
Failed to set assignee to
|
Hm. Maybe it's not correct to seek review from the wg. Not sure who to request instead. r? types |
@bors try @rust-timer queue |
Prefer not to early return from derived visitables LLVM is not able to tail-call optimise the final early return, as there instructions that follow it. Making that call the returned expression resolves this. (As identified in rust-lang#117896 (comment)). r? wg-compiler-performance
☀️ Try build successful - checks-actions |
@rust-timer build 4c24faf |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (4c24faf): 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. 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: 670.936s -> 671.766s (0.12%) |
the perf results seem slightly negative. Do you still want to merge this? |
Let me investigate - had seen quite different results locally, albeit there were other variables at play too. I'll try to isolate them and figure it out! @rustbot author |
LLVM is not able to tail-call optimise the final early return, as there instructions that follow it. Making that call the returned expression resolves this. (As identified in #117896 (comment)).
r? wg-compiler-performance