Support more than one stage when fuzzing a proc with a non-blocking receive
Open
fuzz
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 283
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 135
Description
Currently, when fuzzing a proc with a non-blocking receive, the maximum pipeline stage is one. The latter ensures proper validation of the verilog output with other stages in the proc. To enhance the coverage, the pipeline stages should not be limited to one.
Contributor guide
Assessment
This issue has not been assessed yet.