[hls-fuzzer] Add variable probability table - #1030
Open
zero9178 wants to merge 1 commit into
Open
Conversation
Prior to this PR the choice of variables was fully uniform. There are however use cases where we want specific variables to be more likely to be generated. One such use case e.g. is that loop recurrence variables should be used *after* the loop to make it as likely as possible for the loop to stay alive. (Making it more likely rather than forcing it via discards is easier to implement without destroying program diversity + makes it such that the generator cannot fail to generate a C program)
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
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.
Prior to this PR the choice of variables was fully uniform. There are however use cases where we want specific variables to be more likely to be generated.
One such use case e.g. is that loop recurrence variables should be used after the loop to make it as likely as possible for the loop to stay alive. (Making it more likely rather than forcing it via discards is easier to implement without destroying program diversity + makes it such that the generator cannot fail to generate a C program)