Recently I find that in Genus is supporting function of declaration different clocking domains. Instead using clock groups and than add them as asynchronous, domains seems to ignore all cross-domain relations as well as skipping timing analysis path between them.
So what's the pure advantage of declaration of clock domains? I can set falsepath between clocking groups as well. And any kind of Cadences OTPG we don't use so all features are unable for us.
Also it's pretty strange to find using any kind clock domain settings most in Legacy IU (which I believe become too old for using).
Hi Nick,the command "create_clock -domain" is Genus' way of disabling the timing paths using the tool's native command, whereas "set_clock_groups -asynchronous" is an SDC construct. There is no advantage, both of the methods are working in Genus to disable the timing paths.The existence of both methods has historical reasons, but the current recommendation is to use the SDC format
Related articles: Comparing Genus command “create_clock -domain” and SDC command “set_clock_groups -asynchronous”Why does input SDC constraints differ from write_sdc output ?
From what I understand, it's the clocking paths to the two flip flops on each clocking domain, the difference between the path Speed Test timi s