[hls-fuzzer] Add simplest non-functional LSQ fuzzer#847
Open
zero9178 wants to merge 1 commit intousers/zero9179/bitwidth-read-constraint-flowfrom
Open
[hls-fuzzer] Add simplest non-functional LSQ fuzzer#847zero9178 wants to merge 1 commit intousers/zero9179/bitwidth-read-constraint-flowfrom
zero9178 wants to merge 1 commit intousers/zero9179/bitwidth-read-constraint-flowfrom
Conversation
This PR adds an initial fuzzer for testing LSQ elision in Dynamatic. It uses a type system that is specifically designed to not require any memory ordering. The logic currently used is very simple: Only a single Write-after-Read statement is generated and the write operation is either data- or control dependent on the read operation. Support for more complicated constructs will be added in future PRs. For now this fuzzer already finds suboptimal code in milliseconds.
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.
This PR adds an initial fuzzer for testing LSQ elision in Dynamatic. It uses a type system that is specifically designed to not require any memory ordering.
The logic currently used is very simple: Only a single Write-after-Read statement is generated and the write operation is either data- or control dependent on the read operation. Support for more complicated constructs will be added in future PRs. For now this fuzzer already finds suboptimal code in milliseconds.
Depends on #837