From ddb084e9a8a0cba10536951236cde824526e8071 Mon Sep 17 00:00:00 2001 From: gatecat Date: Sun, 19 Dec 2021 16:41:34 +0000 Subject: archapi: Use arbitrary rather than actual placement in predictDelay This makes predictDelay be based on an arbitrary belpin pair rather than a arc of a net based on cell placement. This way 'what-if' decisions can be evaluated without actually changing placement; potentially useful for parallel placement. A new helper predictArcDelay behaves like the old predictDelay to minimise the impact on existing passes; only arches need be updated. Signed-off-by: gatecat --- docs/archapi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/archapi.md') diff --git a/docs/archapi.md b/docs/archapi.md index f2571f08..5034d7d1 100644 --- a/docs/archapi.md +++ b/docs/archapi.md @@ -517,7 +517,7 @@ result, and for that estimate it is considered more acceptable to return a slightly too high result and it is considered less acceptable to return a too low result (thus "low upper bound"). -### delay\_t predictDelay(const NetInfo \*net\_info, const PortRef &sink) const +### delay\_t predictDelay(BelId src_bel, IdString src_pin, BelId dst_bel, IdString dst_pin) const Return a reasonably good estimate for the total `maxDelay()` delay for the given arc. This should return a low upper bound for the fastest route for that arc. -- cgit v1.2.3