[Synth] Use LinearTimingArcAttr sensitivity in TechMappper
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
Currently, TechMapper only uses LinearTimingArcAttr intrinsic delay. We shall update it to use sensitivity in delay costing. A benefit of this is this would make timing-driven mapping reflect the full arc cost instead of treating non-intrinsic timing data as unused metadata.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating TechMapper and tracing where LinearTimingArcAttr intrinsic delay is read for delay costing. Then inspect how its sensitivity data is represented and used in nearby timing-mapping code. Done means timing-driven mapping includes sensitivity so the full arc cost is reflected rather than treating non-intrinsic timing data as unused metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100