| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces the arch-specific DelayInfo structure with new DelayPair
(min/max only) and DelayQuad (min/max for both rise and fall) structures
that form part of common code.
This further reduces the amount of arch-specific code; and also provides
useful data structures for timing analysis which will need to delay
with pairs/quads of delays as it is improved.
While there may be a small performance cost to arches that didn't
separate the rise/fall cases (arches that aren't currently separating
the min/max cases just need to be fixed...) in DelayInfo, my expectation
is that inlining will mean this doesn't make much difference.
Signed-off-by: gatecat <gatecat@ds0.me>
|
| |
|
|
| |
Signed-off-by: David Shah <dave@ds0.me>
|
| |
|
|
| |
Signed-off-by: David Shah <dave@ds0.me>
|
| |
|
|
| |
Signed-off-by: David Shah <dave@ds0.me>
|
|
|
Signed-off-by: David Shah <dave@ds0.me>
|
