Not Always. CDC(Clock Domain Crossings) analysis required very much in bigger SOC's. If these clock domains are not interacting in any of the functional modes, you can always set false paths. If its interacting, you cant set false path untill and unless , you have any other mechanisam to test /verify these Asynchronous timing checks.
I strongly feel that you have to always use set_false_path or set_clock_group in DC, so that you can avoid the compiler to unnecessarily optimize this path and throw warnings/error . The actual intent is that whenever we make a CDC, then the timing of signal arriving on first flop of the synchronizer is unknown and hence not to be timed.
---------- Post added at 07:59 ---------- Previous post was at 07:58 ----------
Alrighty, false paths should be set when different clock domains are asynchronous. In asynchronous communication the capure flop would be sync flop. sync flops are nothing but a group flops connected back to back to avoid metastability problems.
If they are synchronous, they need to be timed.