-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Use insertvalue
and extractvalue
instead of memcpy
in CastTarget
#128969
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Use `insertvalue` and `extractvalue` instead of `memcpy` in CastTarget r? `@nikic`
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (dba68d9): comparison URL. Overall result: ❌✅ regressions and improvements - 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @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)Results (primary 2.7%)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.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResults (primary -0.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.
Bootstrap: 757.742s -> 756.575s (-0.15%) |
Some changes occurred in compiler/rustc_codegen_gcc |
@rustbot author |
This comment has been minimized.
This comment has been minimized.
I believe the PR is far from being ready for review. The main problem is the incorrect implementation of the cast. In addition to using I'm not sure whether I should perform a complete conversion like SROA does, or if I should just truncate/convert the final value? Do you have any suggestions? @nikic Additionally, I think I could revert the implementation in |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☔ The latest upstream changes (presumably #130473) made this pull request unmergeable. Please resolve the merge conflicts. |
@DianQK any updates on this? thanks |
I'm low on the priority list for this PR. :) |
When I rework on this PR, I'll split it into two separate PRs. |
r? @nikic