Update ALU MULT mode in gowin to match nextpnr #4827
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
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.
nextpnrcurrently wires an ALU inMULTmode in a different fashion than expected. Instead ofI2toGND, it is connected toVCC. This has been mentioned in YosysHQ/nextpnr#1407. While fixing this innextpnrwould work, leaving it as-is is arguably a better option, since it can perform the same operations plus being able to take a second operand. This would have a profound impact if choosing to synthesize multiplication using this mode.So, instead of fixing the wiring in
nextpnr, this PR seeks to update the expected behavior of the cell to reflect the current wiring.yosysdoesn't use this mode yet, and therefore no tests or workflows should be impacted.