-
Notifications
You must be signed in to change notification settings - Fork 13k
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
adjust Miri to needs of changed unwinding strategy #69999
Conversation
r? @davidtwco (rust_highfive has picked a reviewer for you, use r? to override) |
@bors p=1 |
r? @oli-obk |
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.
Seems good, though I wasn't able to quite follow the miri changes.
@@ -272,11 +272,13 @@ impl<'tcx, Tag> Scalar<Tag> { | |||
|
|||
#[inline] | |||
pub fn from_bool(b: bool) -> Self { | |||
// Guaranteed to be truncated and does not need sign extension. |
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.
These seem like they could be separate? But fine to leave them in too.
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.
I had to add from_i32
for the Miri side of this. So while I was at it I figured I might as well add the comments here, instead of making them a separate PR.
r=me with the comment updated. |
@bors r=oli-obk |
📌 Commit b450e1b has been approved by |
☀️ Test successful - checks-azure |
As expected, #67502 broke unwinding in Miri. To fix it we have to adjust parts of the engine and the panic runtime, which this PR does. The Miri-side changes are in rust-lang/miri#1227.
Cc @oli-obk @Aaron1011 @Mark-Simulacrum @Amanieu