| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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 <gatecat@ds0.me>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This Arch API dates from when we were first working out how to
implement placement validity checking, and in practice is little used by
the core parts of placer1/HeAP and the Arch implementation involves a
lot of duplication with isBelLocationValid.
In the short term; placement validity checking is better served by the
combination of checkBelAvail and isValidBelForCellType before placement;
followed by isBelLocationValid after placement (potentially after
moving/swapping multiple cells).
Longer term, removing this API makes things a bit cleaner for a new
validity checking API.
Signed-off-by: gatecat <gatecat@ds0.me>
|
| |
|
|
| |
Signed-off-by: D. Shah <dave@ds0.me>
|
| |
|
|
| |
Signed-off-by: Keith Rothman <537074+litghost@users.noreply.github.com>
|
| |
|
|
| |
Signed-off-by: Keith Rothman <537074+litghost@users.noreply.github.com>
|
| |
|
|
| |
Signed-off-by: D. Shah <dave@ds0.me>
|
| |
|
|
| |
Signed-off-by: David Shah <dave@ds0.me>
|
|
|
Signed-off-by: David Shah <dave@ds0.me>
|
