Add support for the imctk-eqy-engine ("use imctk") #70
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
mmicko
approved these changes
Sep 16, 2024
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.
What are the reasons/motivation for this change?
Supporting the imctk-eqy-engine. This also requires YosysHQ/sby#297 and the imctk-eqy-engine built from the imctk's wip branch (will update this when there's a PR on the imctk repository).
Explain how this is achieved.
By creating a strategy derived from the SBY strategy and adding imctk-eqy-engine to the aiger engines SBY knows about.
If applicable, please suggest to reviewers how they can test the change.
The "picorv32_vivado.eqy" example can be changed to use the "use imctk" strategy instead.