Replies: 1 comment
-
Yes it should be the worst slack path to that endpoint. Total paths is exponential in design size. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is just an observation that puzzled me for a bit that I thought I'd share.
First I thought something was wrong, but having thought about it for a bit, it's obvious: the endpoint slack diagram counts only endpoints, whereas the timing report has all the start and end point combinations. This means that the timing report has many more rows than there are endpoints in the slack diagram.
At least 9999(maximum in GUI) rows here:
Of course this is nothing new, there is a feature to display only one row per endpoint:
Hmm... is that the worst slack per end-point?
Beta Was this translation helpful? Give feedback.
All reactions