Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

030-iob18 uses a hack to work around the fuzzer not discovering RIOB18.IOB_Y0.SSTL*.IN #2073

Open
hansfbaier opened this issue Dec 16, 2022 · 0 comments

Comments

@hansfbaier
Copy link
Collaborator

For some reason the mentioned feature is only discovered for IOB_Y1, but not for IOB_Y0.
What seems to cause this is that the bit 39_127 from the manually identified feature
RIOB18.IOB_Y0.SSTL12_SSTL135_SSTL15.IN !38_126 39_127
disappears, when we have a differential input on IOB_Y0 (but not on IOB_Y1).
This creates a contradiction which makes segmatch report 0 candidates.

The python script to examine this and its output are attached here:
findsegbug.py.gz
result.txt

So, unfortunately currently we are inserting the mentioned feature manually in the Makefile,
which is a hack. It would be better to find out, how we could modify the fuzzer to find
the mentioned feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant