Set port_id for Verific PortBus wires
#5442
Open
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.
What are the reasons/motivation for this change?
port_idis not set for VerificPortBuswires, so those ports can be reordered unexpectedly. This appears to just be an oversight. This results in the following behavior, for example:producing
I realize that Yosys doesn't guarantee port ordering in general, but this still seems bad and is easy to fix.
Explain how this is achieved.
Set the
port_idforPortBuswires to be theport_idof the firstPortassociated with thePortBus, and add a testcase.