Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MIR counterparts to llvm_extract and llvm_compositional_extract #2085

Open
RyanGlScott opened this issue Aug 7, 2024 · 0 comments
Open

MIR counterparts to llvm_extract and llvm_compositional_extract #2085

RyanGlScott opened this issue Aug 7, 2024 · 0 comments
Labels
subsystem: crucible-mir Issues related to Rust verification with crucible-mir and/or mir-json type: enhancement Issues describing an improvement to an existing feature or capability type: feature request Issues requesting a new feature or capability

Comments

@RyanGlScott
Copy link
Contributor

Currently, the MIR backend lacks a way to extract a Rust function into a SAWScript Term. This would be useful in tandem with the prove and sat commands.

To do so, we should make MIR versions of the existing llvm_extract command (which only allows scalar types) and llvm_compositional_extract command (which also allows reference types).
@RyanGlScott RyanGlScott added type: enhancement Issues describing an improvement to an existing feature or capability type: feature request Issues requesting a new feature or capability subsystem: crucible-mir Issues related to Rust verification with crucible-mir and/or mir-json labels Aug 7, 2024
@RyanGlScott RyanGlScott mentioned this issue Aug 16, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
subsystem: crucible-mir Issues related to Rust verification with crucible-mir and/or mir-json type: enhancement Issues describing an improvement to an existing feature or capability type: feature request Issues requesting a new feature or capability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RyanGlScott