-
Notifications
You must be signed in to change notification settings - Fork 352
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
unreachable!() with custom_mir
#2735
Comments
Hm, in principle Miri should work with custom MIR, but also using custom MIR it's possible to write MIR that it is impossible for rustc to otherwise emit, for example because it wouldn't pass borrowck. That said, until someone figures out how to write a proper fuzzer for MIR, it's probably better to have issues like this than not. (I really want to have a fuzzer for MIR) |
Would have to check what happens here, but yeah in principle we should be able to interpret all MIR that passes MIR validation. @JakobDegen is MIR validation being run on custom_mir? (Also makes me wonder whether it is run on shims.)
Stay tuned. ;) |
Yes for custom mir. Shims also have validation run on them, except for drop shims for generators which don't for some reason? See the fixme here |
Oh but looking at the ICE, this should be rejected by validation. We just don't validate retags currently. There should be no |
I would have appreciated if you made a new comment for that. When just reading the notifications emails sent, edits are invisible. :D Yeah that looks wrong... or at least suspicious. See rust-lang/rust#91576. |
Clarify that raw retags are not permitted in Mir Not sure when this changed, but documentation and the validator needed to be updated. This also removes raw retags from custom mir. cc rust-lang/miri#2735 r? `@RalfJung`
Fixed by rust-lang/rust#106012 |
Clarify that raw retags are not permitted in Mir Not sure when this changed, but documentation and the validator needed to be updated. This also removes raw retags from custom mir. cc rust-lang/miri#2735 r? `@RalfJung`
feel free to close if miri is never intended to work with custom mir :)
from
src/test/mir-opt/building/custom/references.rs
The text was updated successfully, but these errors were encountered: