swizzler: add dist constraint retry and fallback #245
Conversation
This file contains hidden or 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
Extends the distribution constraint exploration of the swizzler to retry the values it selects some number of times (4 for now) and if those all fail, fall back to randomizing the field bits as any other variable. The swizzler was only picking one value, and if the given constraints excluded most values then it resulted in the solver tossing it and leaving the field unrandomized, which in many cases lets the solver default to 0 or some other value repeatedly. See fvutils#243
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Extends the distribution constraint exploration of the swizzler to retry the values it selects some number of times (4 for now) and if those all fail, fall back to randomizing the field bits as any other variable.
The swizzler was only picking one value, and if the given constraints excluded most values then it resulted in the solver tossing it and leaving the field unrandomized, which in many cases lets the solver default to 0 or some other value repeatedly.
See #243