crucible-llvm: Generalize LLVMOverride
's ext
parameter
#1184
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the
OverrideSim
action for anLLVMOverride
was assumed to have a fixedext
parameter, namely,LLVM
. While this is intuitively appealing, it turns out not to be necessary. This is because there are only a few operations in theOverrideSim
monad that make essential use of theext
parameter, such as registering or calling a CFG in the given language extension. These operations are unlikely to be used when defining, e.g., overrides for libc functions.The motivation for generalizing the parameter is to enable the reuse of
LLVMOverride
s in other Crucible language extensions that make use of the LLVM memory model, namely, Macaw.