[export-dot] Use timing modeling in DOT legacy mode #34
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.
This commit makes the
export-dottool leverage the new timing modeling infrastructure (the same as for buffer placement) when producing DOTs compatible with legacy Dynamatic. Instead of component delays and latencies being (probably incorrectly) hardcoded inside the DOTPrinter, they are now fetched from a timing database whose path is given as an argument to the tool.Indirectly, this allows us to make meaningful comparisons between the output of the new buffer placement pass and the legacy one, which now both get their component timing models fetched from the same source.
Fixes #18.