verific: add -set_relaxed_checking option #5581
Open
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
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 a
verific -set_relaxed_checkingoption that enables relaxed semantic checking in the Verific frontend.Silimate’s Yosys fork includes an option to relax Verific’s checking rules to allow such designs to be processed.
Upstreaming this option provides users with an explicit, opt-in mechanism to enable relaxed checking while preserving default strict behavior.
The change introduces a boolean option that calls
VeriNode::SetRelaxedChecking(1)when specified. The behavior is fullyguarded under
VERIFIC_SYSTEMVERILOG_SUPPORTand only takes effect when the option is explicitly passed.