OpenROAD
OpenROAD copied to clipboard
print out set_max_delay number in report_checks
Description
I have a set_max_delay -from $fifo_out_pins -to [match_pins .* output 0] 2000 statement in my .sdc file.
It would be nice if somewhere that number was listed below so that I can get confirmation that I'm doing the right thing.
$ report_checks -from fifo_out.fifomem.raddr\[0\]\$_DFF_PN0_/QN -to rdata[5]
Startpoint: fifo_out.fifomem.raddr[0]$_DFF_PN0_
(rising edge-triggered flip-flop clocked by clk_uncore)
Endpoint: rdata[5] (output port clocked by clk_uncore)
Path Group: clk_uncore
Path Type: max
Delay Time Description
---------------------------------------------------------
0.00 0.00 clock clk_uncore (rise edge)
83.07 83.07 clock network delay (propagated)
0.00 83.07 ^ fifo_out.fifomem.raddr[0]$_DFF_PN0_/CLK (DFFASRHQNx1_ASAP7_75t_R)
48.37 131.44 ^ fifo_out.fifomem.raddr[0]$_DFF_PN0_/QN (DFFASRHQNx1_ASAP7_75t_R)
18.82 150.26 ^ rebuffer38/Y (BUFx3_ASAP7_75t_R)
16.08 166.34 ^ max_cap59/Y (BUFx16f_ASAP7_75t_R)
16.79 183.14 ^ max_cap58/Y (BUFx16f_ASAP7_75t_R)
10.18 193.31 v _40892_/Y (NAND2x1_ASAP7_75t_R)
25.52 218.84 v _40893_/Y (OA211x2_ASAP7_75t_R)
25.28 244.11 v _40894_/Y (OR3x1_ASAP7_75t_R)
14.83 258.95 v _40895_/Y (OA21x2_ASAP7_75t_R)
13.10 272.05 v output49/Y (BUFx2_ASAP7_75t_R)
0.01 272.06 v rdata[5] (out)
272.06 data arrival time
1000.00 1000.00 clock clk_uncore (rise edge)
0.00 1000.00 clock network delay (propagated)
-10.00 990.00 clock uncertainty
0.00 990.00 clock reconvergence pessimism
-800.00 190.00 output external delay
190.00 data required time
---------------------------------------------------------
190.00 data required time
-272.06 data arrival time
---------------------------------------------------------
-82.06 slack (VIOLATED)
Suggested Solution
No response
Additional Context
No response
Or perhaps this is a more general problem: I want to know what I asked OpenSTA to do.... There is a big leap from constraints.sdc to 2_floorplan.sdc and 2_floorplan.sdc doesn't contain information about what OpenSTA concluded it should do based on the input constraints.sdc file.
Perhaps write_sdc could add more comments?