aboutsummaryrefslogtreecommitdiffstats
path: root/docs/coding.md
diff options
context:
space:
mode:
authorgatecat <gatecat@ds0.me>2021-12-19 18:46:10 +0000
committerGitHub <noreply@github.com>2021-12-19 18:46:10 +0000
commit62a3e093856063180526b7189d5e711a98036fa0 (patch)
treed03ba5688367cb476a06b19d04ca78d0352afce3 /docs/coding.md
parent56d550733346000584b9490fac0953fe07124035 (diff)
parentddb084e9a8a0cba10536951236cde824526e8071 (diff)
downloadnextpnr-62a3e093856063180526b7189d5e711a98036fa0.tar.gz
nextpnr-62a3e093856063180526b7189d5e711a98036fa0.tar.bz2
nextpnr-62a3e093856063180526b7189d5e711a98036fa0.zip
Merge pull request #883 from YosysHQ/gatecat/new-predictdelay
archapi: Use arbitrary rather than actual placement in predictDelay [breaking change]
Diffstat (limited to 'docs/coding.md')
-rw-r--r--docs/coding.md2
1 files changed, 1 insertions, 1 deletions
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