Forum Discussion
Altera_Forum
Honored Contributor
16 years agoI would actually recommend not having -use_tan_name. It doesn't hurt, but I see it less and less, and always opens the question of "Why did you have that option on?". THe reason it was created was for the QSF2SDC conversion, whereby the user might have another constraint, like Cut Paths, between two clocks in TAN. If TimeQuest gvae the clocks different names, that Cut Paths conversion would no longer match the clock names and be ignored. But if you don't have that situation, go ahead and get rid of that option, or get rid of it and change the names in your set_false_path to reflect the new clock names. You can see the names by double-clicking the task Report Clocks.
(And this is a really minor suggestion. I'm guessing there will be designs still using that option 10 years from now and having no problems, just pointing out why it's there...)