Forum Discussion
Altera_Forum
Honored Contributor
18 years agoI thought of a possible explanation for what bothered me in my previous post, but I didn't test it to see whether TimeQuest works this way.
Maybe for the transfer table to say "false path", the false-path has to be done from clock domain to clock domain instead of another way like from a particular source register to a particular destination register. If that's the case and paths that are false because of "set_false_path -from src_reg -to dst_reg" get listed in the transfer table with a number (even if all paths on the row of the table are actually false), then it would make sense that you could have all 720 paths in question cut with a register-to-register false-path exception, keeping report_timing from listing anything even though the transfer table doesn't say "false".