-
Notifications
You must be signed in to change notification settings - Fork 12
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
Infrastructure: Add mechanism to validate SMIR #16
Milestone
Comments
As a minimal first step we could create a dummy "codegen" that doesn't even monomorphize, but just tries to generate the MIR of all public items and all items needed by them. Edit: ah you already said that in the linked issue |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Aug 1, 2023
Cover statements for stable_mir Added missing statements to stable_mir, used opaque types for few types that are only used for diagnostic. cc rust-lang/project-stable-mir#16 r? `@oli-obk`
@rustbot claim |
github-actions bot
pushed a commit
to rust-lang/miri
that referenced
this issue
Aug 2, 2023
Cover statements for stable_mir Added missing statements to stable_mir, used opaque types for few types that are only used for diagnostic. cc rust-lang/project-stable-mir#16 r? `@oli-obk`
@rustbot claim |
We added a regression suite and and dummy driver that inspect and test SMIR in #25 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need a better mechanism to validate StableMIR translation. Maybe a mini-interpreter or at least create a debug option that we can inspect.
The text was updated successfully, but these errors were encountered: