-
Notifications
You must be signed in to change notification settings - Fork 415
Create VPR timing report on unconstrained paths #1022
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
Comments
This issue has been inactive for a year and has been marked as stale. It will be closed in 15 days if it continues to be stale. If you believe this is still an issue, please add a comment. |
This issue has been marked stale for 15 days and has been automatically closed. |
This is a useful issue that we never resolved. Sending to @AlexandreSinger to see if he wants to take a crack at it, as he's messing about with SDC files right now. Basically we could produce a report on which clock nets had no timing constraint at least. |
I'll reopen this issue since it is something I may want to look into if I find the time! |
See #1013 .
This is to track item 4 from that issue -- creating a report on unconstrained paths (clocks in particular, but also can include IO->reg paths and so on).
Proposed Behaviour
We should produce a report on unconstrained paths in final timing sign off.
Possibly we should also produce a big warning if we find nothing to optimize (but I'm not sure if that behaviour is easy to trigger given the other fixes in #1013, so perhaps a report is enough).
Current Behaviour
We create default constraints on all clocks if there is no sdc and obey the sdc if there is one. We don't produce any report on how much of the design the sdc constrains.
The text was updated successfully, but these errors were encountered: