update metrics gcd asap7 - #4481
Conversation
Signed-off-by: Jonas Gava <jfgava@precisioninno.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the OpenROAD subproject commit and adjusts several baseline design rules and timing metrics in rules-base.json. Feedback highlights a significant degradation in the global routing setup TNS (globalroute__timing__setup__tns), suggesting a need to analyze the global routing stage for potential congestion or optimization issues rather than just updating the threshold.
| }, | ||
| "globalroute__timing__setup__tns": { | ||
| "value": -206.0, | ||
| "value": -282.0, |
There was a problem hiding this comment.
The timing metric 'globalroute__timing__setup__tns' shows a significant degradation of approximately 37% (from -206.0 to -282.0). While other timing metrics like 'cts__timing__setup__ws' and 'finish__timing__setup__ws' have improved, this large degradation in global routing TNS suggests potential routing congestion or optimization issues introduced by the OpenROAD update. It is recommended to analyze the global routing stage to identify the cause of this regression rather than simply relaxing the regression threshold.
|
Related to PR #11255 |
🔍 QoR checkMetrics reflect the PR merge build — i.e. what will land on the target branch. Advisory — results are log-only and do not affect build status. The authoritative QoR gate remains the local rules-file check. Commit 63 design(s) checked — 1 with regression(s), 1 without a comparable baseline.
❌ asap7/riscv32i-mock-sram base — 1 failing metric(s)
|
2 participants
designs/asap7/gcd/rules-base.json updates: