himbaechel: Initial timing support #1200
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: gatecat <[email protected]>
gatecat
force-pushed
the
gatecat/himbaechel-timing
branch
from
e5837d3
to
50c4952
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This currently WIP and will probably end up landing after #1184.
Remaining issues are adding support for setting node/wire timings in the Python API as well as pip timings; and adding more examples of how this structure could be used to implement different timing models - like configurable cell types, and the spectrum from simple fixed pip delays to fanout-dependent delays (without RC data) to a full RC model.
The RC model implementation is also currently incomplete, but should be good enough for a context where most of the delays are on the pips and it's used to implement a small fanout penalty.