diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/archapi.md | 2 | ||||
| -rw-r--r-- | docs/coding.md | 2 |
2 files changed, 2 insertions, 2 deletions
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. diff --git a/docs/coding.md b/docs/coding.md index dc09bb3f..db2ec079 100644 --- a/docs/coding.md +++ b/docs/coding.md @@ -80,7 +80,7 @@ As nextpnr allows arbitrary constraints on bels for more advanced packer-free fl There are several routes for timing information in the placer: - sink `PortRef`s have a `budget` value annotated by calling `assign_budget` which is an estimate of the maximum delay that an arc may have - sink ports can have a criticality (value between 0 and 1 where 1 is the critical path) associated with them by using `get_criticalities` and a `NetCriticalityMap` - - `predictDelay` returns an estimated delay for a sink port based on placement information + - `predictDelay` and its derivative `predictArcDelay` returns an estimated delay for a sink port based on placement information ### Bel Buckets |