Tighten design - #4485
Conversation
There was a problem hiding this comment.
Code Review
This pull request increases the core utilization to 80 and tightens the clock period from 7.5ns to 6.0ns for the jpeg design on the gf180 platform, updating the baseline rules to match. However, the review points out a critical issue where the worst setup slack (finish__timing__setup__ws) has degraded to -0.523, meaning the design fails to meet timing under the new clock period. Codifying this negative slack in the baseline rules allows timing-failing designs to pass CI.
🔍 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 62 design(s) checked — 0 with regression(s), 0 without a comparable baseline.
|
394ddbb to
7ad95f8
Compare
|
@rafaelmoresco Could you merge latest master to ensure your changes to the design still work? |
Signed-off-by: rafaelmoresco <rafaelmorescovieira@gmail.com>
7ad95f8 to
717baaa
Compare
|
@eder-matheus rebased on master, continues with negative slack. |
gf180 Jpeg
Core utilization: 45 => 80
Clock period: 7.5 => 6.0