Skip to content

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

Open
vaughnbetz opened this issue Oct 30, 2019 · 4 comments
Open

Create VPR timing report on unconstrained paths #1022

vaughnbetz opened this issue Oct 30, 2019 · 4 comments
Assignees
Labels
tatum Tatum timing analyzer

Comments

@vaughnbetz
Copy link
Contributor

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.

Copy link

github-actions bot commented May 1, 2025

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.

@github-actions github-actions bot added the Stale label May 1, 2025
Copy link

This issue has been marked stale for 15 days and has been automatically closed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2025
@vaughnbetz
Copy link
Contributor Author

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.
We might also do the same for IO paths, which might be a little more involved.
More involved still would be to do check the timing tags at the end of a timing analysis to see if we had found paths between registers where we don't know any timing constraint between them.

@AlexandreSinger
Copy link
Contributor

I'll reopen this issue since it is something I may want to look into if I find the time!

@github-actions github-actions bot removed the Stale label May 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tatum Tatum timing analyzer
Projects
None yet
Development

No branches or pull requests

2 participants