Support llvm_extract
, llvm_compositional_extract
, jvm_extract
, etc. in the Python bindings
#2092
Labels
subsystem: crucible-jvm
Issues related to Java verification with crucible-jvm
subsystem: crucible-llvm
Issues related to LLVM bitcode verification with crucible-llvm
subsystem: saw-python
Related to the Python bindings for the RPC SAW server
subsystem: saw-remote-api
Issues related to the SAW server and its RPC bindings
type: feature request
Issues requesting a new feature or capability
Milestone
Currently, the
llvm_extract
family of SAWScript commands do not have counterparts in the SAW Python bindings. I would like to ensure feature parity between SAWScript and Python when adding support for MIR versions of these commands (see #2085), and this issue is a prerequisite for that.In the spirit of the existing design of the Python bindings, I propose that we add
extract
andcompositional_extract
Python functions, which choose the appropriate language backend under the hood (e.g.,llvm_extract
for LLVM orjvm_extract
for JVM). Not all language backends would be supported at this time—for instance, there is currently nojvm_compositional_extract
function (see #1039), so calling the Pythoncompositional_extract
function with JVM verification would be an error.The text was updated successfully, but these errors were encountered: