-
Notifications
You must be signed in to change notification settings - Fork 13.3k
proc_macro/bridge: remove #[repr(C)]
from non-ABI-relevant types.
#98224
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
This comment was marked as off-topic.
This comment was marked as off-topic.
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
The handle store seems to be used by the server at
|
@bjorn3 Yeah but that's all server-side, it doesn't cross the client<->server ABI boundary. |
I see. In that case r=me if there is no perf regression. |
It wouldn't surprise me too much if at one point in the design process, the ident for |
Wait, the try build never triggered? @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 83545d3 with merge 49b8138e769dd54cfcc5251d464bed219728c2c9... |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
(spurious network failures) @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 83545d3 with merge fad3f20b02202d8b125bfde50f2aed80e525fb08... |
☀️ Try build successful - checks-actions |
Queued fad3f20b02202d8b125bfde50f2aed80e525fb08 with parent 5fb8a39, future comparison URL. |
Finished benchmarking commit (fad3f20b02202d8b125bfde50f2aed80e525fb08): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
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 may lead to changes in compiler perf. @bors rollup=never Footnotes |
@bors r+ |
📌 Commit 83545d3 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2b646bd): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Not sure how this happened, maybe some of these were passed through the bridge a long time ago?
r? @bjorn3