Concretization: Getting concrete RegValues from a model
#1207
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
langston-barrett
force-pushed
the
lb/concretize
branch
3 times, most recently
from
6c3f670 to
8421be4
Compare
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:
int f(int x, int y) { return x / (y - 2); }
it would be nice to say which particular values of `x` and `y` 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.
langston-barrett
force-pushed
the
lb/concretize
branch
from
8421be4 to
5235cea
Compare
RyanGlScott
reviewed
Jun 5, 2024
langston-barrett
force-pushed
the
lb/concretize
branch
from
863e5ec to
aaec2b4
Compare
RyanGlScott
approved these changes
Jun 6, 2024
langston-barrett
force-pushed
the
lb/concretize
branch
from
aaec2b4 to
eb8c20e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
xandywould 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.