Timing analysis is available anywhere in the flow after synthesis. You can review the Timing Summary report files automatically created by the Synthesis and Implementation runs.
If your synthesized or implemented design is loaded in memory, you can also generate an interactive Timing Summary report from:
The equivalent Tcl command is report_timing_summary.
For more information on the report_timing_summary options, see this link in the
Vivado
Design Suite Tcl Command Reference Guide (UG835).
In a synthesized design, the Vivado® IDE timing engine estimates the net delays based on connectivity and fanout. The accuracy of the delays is greater for nets between cells that are already placed by the user. There can be larger clock skew on paths where some of the cells have been pre-placed, such as I/Os and GTs.
In an implemented design, the net delays are based on the actual routing information. You must use the Timing Summary report for timing signoff if the design is completely routed. To verify that the design is completely routed, view the Route Status report.
When run from the Tcl Console or the GUI, the Timing Summary report can
be scoped to one or more hierarchical cells using the -cells option. When the report is scoped, only paths with the datapath
section that start, end, cross, or are fully contained inside the cell(s) are
reported.
When run from the Tcl Console, the first section of the report is a
summary of the methodology violations from the latest
report_methodology run. This section is not available when
report_timing_summary is run from the GUI. When
report_methodology has not been run prior to
report_timing_summary, the section is empty. If any design change
has been implemented since the last report_methodology run, the
violations summary might not be up to date.