-
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
Partially move cg_ssa towards using a single builder #94123
Conversation
Some changes occured to rustc_codegen_gcc cc @antoyo |
r? @lcnr (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
9611fba
to
b8ff4bd
Compare
@bors try @rust-timer queue just in case. Don't expect a lot of change though. |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit b8ff4bdd5cd50881c9dd47442f50c333261ba4e7 with merge f7c9ff1f47173b2462d35a513f564b40e1e0f380... |
There is a small bug in the last commit only affecting cg_gcc. I will push a fix tomorrow. |
☀️ Try build successful - checks-actions |
Queued f7c9ff1f47173b2462d35a513f564b40e1e0f380 with parent b8c56fa, future comparison URL. |
Finished benchmarking commit (f7c9ff1f47173b2462d35a513f564b40e1e0f380): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 led to changes in compiler perf. @bors rollup=never |
97301ed
to
5bc81b1
Compare
Split out the cg_gcc changes where possible to my Ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
☔ The latest upstream changes (presumably #92911) made this pull request unmergeable. Please resolve the merge conflicts. |
5bc81b1
to
cc0bdfb
Compare
@bors r=antoyo,tmiasko |
📌 Commit cc0bdfb1e01841994ce7554d08858b5d978c9744 has been approved by |
r? @tmiasko |
⌛ Testing commit cc0bdfb1e01841994ce7554d08858b5d978c9744 with merge 8c5e5f64093e81f763582226630dd7814ea65335... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Could you squash the fix into commit that made the change? Feel free to r+ when done. |
ede54a1
to
96cf799
Compare
@bors r=tmiasko |
📌 Commit 96cf799 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (3d127e2): comparison url. Summary: This benchmark run shows 4 relevant improvements 🎉 to instruction counts.
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
…iasko Partially move cg_ssa towards using a single builder Not all codegen backends can handle hopping between blocks well. For example Cranelift requires blocks to be terminated before switching to building a new block. Rust-gpu requires a `RefCell` to allow hopping between blocks and cg_gcc currently has a buggy implementation of hopping between blocks. This PR reduces the amount of cases where cg_ssa switches between blocks before they are finished and mostly fixes the block hopping in cg_gcc. (~~only `scalar_to_backend` doesn't handle it correctly yet in cg_gcc~~ fixed that one.) `@antoyo` please review the cg_gcc changes.
Not all codegen backends can handle hopping between blocks well. For example Cranelift requires blocks to be terminated before switching to building a new block. Rust-gpu requires a
RefCell
to allow hopping between blocks and cg_gcc currently has a buggy implementation of hopping between blocks. This PR reduces the amount of cases where cg_ssa switches between blocks before they are finished and mostly fixes the block hopping in cg_gcc. (onlyfixed that one.)scalar_to_backend
doesn't handle it correctly yet in cg_gcc@antoyo please review the cg_gcc changes.