Using 'set_clock_groups' without parameter -asynchronous or -exclusive?

[Altera_Forum]

Hi, 

 From the Quartus user manual "Quartus II Handbook Version 9.1 Volume 3: Verification":  set_clock_groups [-asynchronous | -exclusive] -group <clock name> [-group <clock name>] [-group <clock name>] ...  a group is defined with the -group option. the timequest timing analyzer cuts the timing paths between clocks each of the separate -groups groups.  I tried to use following constrain in SDC file:  set_clock_groups  -group [get_clocks {CLK_A}]  -group [get_clocks {CLK_B}]  But TimeQuest still reports violation of paths between domain CLK_A and CLK_B.  Am I miss-understanding something???  # . PS: NO violation is reported if I use:  set_clock_groups -asynchronous -group [get_clocks {CLK_A}]  -group [get_clocks {CLK_B}]  OR  set_clock_groups -exclusive  -group [get_clocks {CLK_A}]   -group [get_clocks {CLK_B}]

[Altera_Forum]

Looks like an issue with the documentation then. It should indeed be set_clock_groups -asynchronous to specify that the clocks are unrelated. Leaving out the -asynchronous or -exclusive actually tells Timequest that the domains _are_ related. 

 Best regards,   Ben

[Altera_Forum]

Strange. When I run it without those options I get an error: 

At least one of the following options are required: -asynchronous, -exclusive Are you sure you're not seeing this? Regardless, you need one of those options for that command.

[Altera_Forum]

Hi Rysc, 

 You are right!  My wrong that forget to check the log first, thanks.    --- Quote Start ---  Strange. When I run it without those options I get an error: At least one of the following options are required: -asynchronous, -exclusive   --- Quote End ---