You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
try makes a best-effort attempt to recover from panics - if the code in the first function pointer crashes with a panic, rust will try to run the cleanup code in the second function pointer.
It is not clear to me what the right semantics are here. For now, handling this as a unimplemented allows us to soundly move forward, but it might be more accurate to actually call the first function pointer. I don't know of a nice way to do the unwinding on panic - maybe CBMC has a mechanism?
Activity
danielsn commentedon Jun 29, 2021
Test case added in
cbmc/Intrinsics/fixme_try.rszhassan-aws commentedon Mar 18, 2022
trylikely requires the panic unwind strategy (doesn't work with abort).[-]`try` intrinsic is unimplemented, but required for firecracker[/-][+]Unimplemented: `try` intrinsic[/+][-]Unimplemented: `try` intrinsic[/-][+]Unimplemented: `catch_unwind` intrinsic[/+]adpaco commentedon Mar 1, 2024
Renamed the issue since
trywas renamed tocatch_unwindin rust-lang/rust#121598Fix stale signature assertion for the catch_unwind intrinsic (model-c…
intrinsics: stop ICEing on catch_unwind signature drift across rustc …
Accept any return type for the unimplemented `catch_unwind` intrinsic
Don't ICE when rustc changes the return type of `catch_unwind`
Don't ICE when rustc changes the return type of `catch_unwind` (model…