Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
14 years ago

timequest timing analyzer spend too much time to report timing

The timequest timing analyzer spend too much time(exceed 6hours) to report timing on one big hold violation path. I use quartusII/10.1sp1. Anyone have similar experience on it? Thanks a lot
Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
14 years ago

You mean you do something like:

report_timing -hold -npaths 1 -from/-to -panel_name "long_report"

and it takes 6 hours to return? Or does that include the creation of the timing netlist, reading in the .sdc, etc.? Or is it the TQ time during a full compile?

(None of that should take 6 hours, but just trying to understand)