Guard unsynthesizable $isunknown with ifndef SYNTHESIS
#239
Conversation
This file contains 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
niwis
approved these changes
Oct 7, 2024
colluca
approved these changes
Oct 7, 2024
michael-platzer
deleted the
michael-platzer/fix/unsynthesizable-isunknown
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While working on #233, I overlooked that the combinatorial blocks around the immediate assertions in
addr_decode_dyncandmultiaddr_decodecontain an unsynthesizable$isunknown()call. While the guard macros inassertions.svhdo disable the assertions themselves whenSYNTHESISis defined, the$isunknownrequires that the whole block is guarded as well. Sorry for missing this!