Concretization: Getting concrete RegValue
s from a model
#1207
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.
What4 has the capacity to turn symbolic values into plausible "concrete" (/"ground") values, given a model from the SMT solver (
GroundEvalFn
). This commit builds on this feature to enable concretizing more complex Crucible types.A possible use-case is to present concrete instances where safety assertions fail, e.g. when symbolically executing the following function:
it would be nice to say which particular values of
x
andy
would cause either signed underflow (y < INT_MIN + 2
) or division by zero (y == 2
). This particular case could be handled by existing What4 functionality, but the same motivation applies to more complex cases involving Crucible-specific types.