Skip to content

Commit da531c5

Browse files
committed
EndpointSlackTracking.md: *-failed .odb files get no snapshot
write_endpoint_slack returns early for a *-failed step; the previous commit said they get one. Any other .odb written through orfs_write_db, an ad-hoc checkpoint among them, does. Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
1 parent c841eea commit da531c5

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎docs/contrib/EndpointSlackTracking.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ Every step then writes `$(REPORTS_DIR)/<step>_endpoint_slack.json`, e.g.
2424
It works in the single-process `flow/scripts/flow.tcl` flow as well. Steps
2525
that just copy their input (`orfs_copy_db`, e.g. `5_3_fillcell` without fill
2626
cells) re-time the design if it is loaded, or else copy the previous step's
27-
snapshot. Other `.odb` files written through `orfs_write_db`, such as a
28-
step's `<step>-failed.odb`, also get a snapshot.
27+
snapshot. Any other `.odb` written through `orfs_write_db`, such as an
28+
ad-hoc checkpoint, also gets a snapshot; `*-failed` ones don't.
2929

3030
A placed step is timed with the parasitics OpenROAD has for it: a bare
3131
`estimate_parasitics` estimates from the global routes when there are any,

0 commit comments

Comments
 (0)