how DC handle multicycle path check

xiaoyisimonguo

How Design compiler handle multicycle path checkfor instance, in this:
set_multicycle_path 2 -to mult/product*

DC will check setup time violations on the second capture clock rising edge, after the launch clock, right?

what about hold time violation? at the rise edge of the launch clock? or the first capture clock?

It makes more sense the first capture clock.
Do we have a way to specify to DC?

churchmice

你直接dc里面man set_multicycle_path
里面把setup/hold这几个参数研究一下就有的事情，有必要发一堆鸟语在论坛上吗？

xiaoyisimonguo

回复 2# churchmice

Thank you for your responseMy confusion came from the man page:
"If neither  -hold nor -setup are specified, path_multiplier is used
              for setup, and 0 is used for hold."

path_multiplier is used for setup, in my case 2 is easy to understand, and was just what I thought

But "0 is used for hold", does that mean DC is checking against the launch clock, rather than the 1st receiving
clock.

Is there a way in DC I could see how DC apply path_multiplier to the calculations of setup and hold check?

Many thanks