|
<h3 id='___report_timing'>report_timing</h3> |
|
<pre>Timing command. Report timing |
|
<b>Usage:</b> report_timing(@options); |
|
@options: |
|
-help: Prints this information |
|
-delay_type $delay_type: Specifies the type of path delay: max (default) or min |
|
-from: $startpoint, Starting point of the timing report |
|
-to: $endpoint, Ending point of the timing report |
|
-through: $through_points, Through points, the value can be an array point |
|
-thr_and: Through points should all present |
|
-max_paths number: Max path number to report, if it is not set, only report one path |
|
-all: Reports all timing paths |
|
-input_pins: Displays input pins of instances |
|
-nosplit: Prevents line splitting |
|
<b>Note:</b> If none of the 'from' or 'to' or 'through' option is present, the timing report is on the paths that go through the ECO instances |
|
|
|
<b>Examples:</b> |
|
|
|
#1. Report timing on the paths that go through the ECO instances |
|
report_timing(); |
|
|
|
#2. Report timing on the instances that in through option |
|
my $thr_instances = ["u_control/u_clk/U120", "u_control/u_mbist/U117"]; |
|
report_timing("-through", $thr_instances); |
|
|
|
#3. Report timing on the instances that in through option and they should all appear in the report path |
|
my $thr_instances = ["u_control/u_clk/U120", "u_control/u_mbist/U117"]; |
|
report_timing("-through", $thr_instances, "-thr_and"); |
|
|
|
</pre> |