title: What is the difference between set_false_path Vs. set_clock_group?
body: <p>I've got a question about the Design compiler's constraints.
  Especially, set_false_path Vs. set_clock_group.</p>
  <p>As I know,</p>
  <ol>
  <li>set_false_path</li>
  </ol>
  <blockquote>
  <p>(a) set_false_path -from [get_clocks CLKA] -to [get_clocks CLKB]].</p>
  </blockquote>
  <p>I think this is considering about one way direction.</p>
  <blockquote>
  <p>(b) set_false_path -from [get_clocks CLKA] -to [get_clocks CLKB]]</p>
  <p>set_false_path -from [get_clocks CLKB] -to [get_clocks CLKA]]</p>
  <p>-&gt; CLKA -&gt; CLKB, CLKB -&gt; CLKA (Bi-Direction)</p>
  </blockquote>
  <ol start="2">
  <li>set_clock_groups</li>
  </ol>
  <blockquote>
  <p>(a) set_clock_groups -asynchronous -group CLKA -group CLKB</p>
  </blockquote>
  <p>I think this is considering about Bi-direction.</p>
  <p>So here is my question
  I think there is only difference between set_false_path and set_clock_group is only direction.</p>
  <p>Then I think 1.(b) and 2.(a) are the same. so then can I use 2.(a) instead 1.(b)?</p>