-
Notifications
You must be signed in to change notification settings - Fork 24
Add support for rawTerm
to Python bindings
#908
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
Conversation
05c9709
to
23e9e5e
Compare
Co-authored-by: Tamás Tóth <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Python part looks good.
Test in pyk: runtimeverification/pyk#748
Part of: #905 In #905, we are implementing a Python binding for the backend's function evaluator: given a function label and list of argument `Pattern`s, construct runtime terms for the arguments, evaluate the function with the given label, and return the result as an AST pattern. To safely reify the runtime term produced by the function call to an AST pattern, we need to know its sort (so that the machinery in #907, #908 can be used correctly). In some places in the bindings, we have to require that callers provide a sort when reifying terms back to patterns. However, when calling a function, the label of the function determines precisely the correct sort to use. This PR emits a new table of global data into compiled interpreters that maps tags to declared return sorts, along with a function that abstracts away indexing into this table. This change is similar to (but simpler than) an existing table of _argument sorts_ for each symbol that we already emit. Testing is handled by binding the new function to Python.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming that the changes on the function signatures don't break anything on pyk and on python's bindings, The c++ part LGTM!
~Blocked on runtimeverification/llvm-backend#908 --------- Co-authored-by: devops <[email protected]>
This PR adds a new feature to the backend's binding API that allows for function symbols to be evaluated on a set of AST pattern arguments, with the result returned as a pattern also. This is motivated by the proof generation project; the execution trace format generated by the backend to summarise a concrete execution can contain the labels and arguments for function call events, but not the functions' return values without breaking tail-call optimisation. Most of the prerequisite work for this PR was done in #908 and #911; the actual changes here are quite small: * Adds a sort-aware term-to-pattern reification method that uses the new `rawTerm{}` wrapper. * Marshals arguments and returns between pattern and term level in the core bindings API. * Adds a test case demonstrating a few simple cases for this feature; as ever the bulk of the testing ought to be performed in Pyk.
~Blocked on runtimeverification/llvm-backend#908 --------- Co-authored-by: devops <[email protected]>
…erification/pyk#748) ~Blocked on runtimeverification/llvm-backend#908 --------- Co-authored-by: devops <[email protected]>
…erification/pyk#748) ~Blocked on runtimeverification/llvm-backend#908 --------- Co-authored-by: devops <[email protected]>
…erification/pyk#748) ~Blocked on runtimeverification/llvm-backend#908 --------- Co-authored-by: devops <[email protected]>
…erification/pyk#748) ~Blocked on runtimeverification/llvm-backend#908 --------- Co-authored-by: devops <[email protected]>
Blocked on #907This PR follows up #907 by having the Python bindings strip patterns of the form
rawTerm{}(inj{...}(...)})
when deserializing from binary KORE; this will allow Pyk and subsequently the proof checker's parser to soundly load function arguments from proof traces and pass them to the function evaluator in #905.