-
Notifications
You must be signed in to change notification settings - Fork 409
[Analysis] Printing Nets timing Information #3023
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…e the report by default
…rilog-to-routing into routing_path_timing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @amin1377 , this is a very great PR! Some comments below.
… generate the report by default" This reverts commit b8289db.
…rilog-to-routing into routing_path_timing
Thanks for the comments Alex, always appreciate it! I’ve addressed them; feel free to resolve if you don’t have any further suggestions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Amin.
I recommend also adding this to the documentation (currently it is only in the help menu), but I leave it up to you how much visibility you want to give this option.
In this PR, a new function is added to generate a report showing the pin delay and slack for each net in the following format:
Below is part of the output for the Titan
ucsb_152_tap_fir_stratixiv_arch_timing
circuit: