Fix crash populating design with special nets #23
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
When a Reader is reading a design and both a verilog and a def file are used for the description of the design, the special nets are only defined in the def and not in the verilog. This fix allows the definition of normal nets from the verilog file, and adds the definitions of the special nets from the def file.
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.
When a Reader is reading a design and both a verilog and a def file are
used for the description of the design, the special nets are only
defined in the def and not in the verilog.
This fix allows the definition of normal nets from the verilog file, and
adds the definitions of the special nets from the def file.