Node naming, including hierarchical history in Yosys+Odin-II #2086
Conversation
This file contains hidden or 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
sdamghan
added
the
Yosys+Odin-II
sdamghan
force-pushed
the
yosys_odin_net_names
branch
from
282ed2b to
b0c5de9
Compare
7 tasks
sdamghan
force-pushed
the
yosys_odin_net_names
branch
5 times, most recently
from
59b0404 to
f0442e8
Compare
sdamghan
force-pushed
the
yosys_odin_net_names
branch
2 times, most recently
from
7a133be to
191330a
Compare
…ut pin name, (should be unique for each subcircuit) to enhance the readability and ease of CP tracking in VTR final timing analysis Signed-off-by: Seyed Alireza Damghani <[email protected]>
sdamghan
force-pushed
the
yosys_odin_net_names
branch
from
d943a46 to
3defc89
Compare
…hical naming style instead of node-type-encoded naming, when extracting names from Yosys coarse-grained BLIF file Signed-off-by: Seyed Alireza Damghani <[email protected]>
Signed-off-by: Seyed Alireza Damghani <[email protected]>
…ic/hdl_include** config files Signed-off-by: Seyed Alireza Damghani <[email protected]>
sdamghan
force-pushed
the
yosys_odin_net_names
branch
from
3defc89 to
549e334
Compare
7 tasks
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.
Signed-off-by: Seyed Alireza Damghani [email protected]
Description
As Yosys generates a coarse-grained BLIF file for Odin-II partial mapper, all BLIF components were interpreted as black boxes at the beginning of Odin-II partial mapping. Therefore, node names were generated based on the type of each subcircuit, which was a unique name and did not include hierarchical information about modules/submodules. This PR extracts the hierarchical information related to each node from the name of its output signals and then sets the node(and its nets) name(s) based on the operation type of each node and the hierarchical information.
P.S: the similar approach is taken in Odin-II, which makes the readability of netlists better and eases the tracking of the critical path in the final VTR timing analysis.
Related Issue
Motivation and Context
How Has This Been Tested?
Types of changes
Checklist: