-
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
abort_internal is safe #72289
abort_internal is safe #72289
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
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.
r=me but I agree it makes sense to wait and rebase atop the other PR, also left a nit.
@bors r+ rollup |
📌 Commit bdbe35d has been approved by |
…ulacrum abort_internal is safe `sys::abort_internal` is stably exposed as a safe function. Forward that assumption "inwards" to the `sys` module by making the function itself safe, too. This corresponds to what rust-lang#72204 did for the intrinsic. We should probably wait until that lands because some of the intrinsic calls in this PR might then need adjustments.
Fixed SGX compilation. @bors r=Mark-Simulacrum |
📌 Commit 2764673 has been approved by |
@bors rollup- |
⌛ Testing commit 2764673 with merge 834d75db38f66b1f2e900118829f05d3b36c1e3e... |
yield |
☀️ Test successful - checks-azure |
sys::abort_internal
is stably exposed as a safe function. Forward that assumption "inwards" to thesys
module by making the function itself safe, too.This corresponds to what #72204 did for the intrinsic. We should probably wait until that lands because some of the intrinsic calls in this PR might then need adjustments.