A worked mechanism
The smallest hold margin can veto a setup win.
This illustrative useful-skew experiment applies the same +0.05 ns capture shift to three same-clock paths; physical reanalysis can change the exact deltas.
Setup-critical path
Setup passes
Baseline −0.03 ns setup becomes +0.02 ns.
Hold path A
Hold still passes
Baseline +0.08 ns hold becomes +0.03 ns.
Hold path B
Hold regresses
Baseline +0.02 ns hold becomes −0.03 ns.
Release decision
ECO not yet accepted
A passing setup headline does not close the affected endpoint set.
Work it through
One clock sink participates in several checks
The setup gain is +0.05 ns while each stated hold margin loses 0.05 ns. Path B blocks release despite the improved setup path.
Evaluate the intersection of required views and paths.
Watch for this
Do not apply a fixed skew benefit to unrelated clock relationships; inspect each actual launch and capture path.
Check your reasoning
Collect the affected sink set, setup/hold differences, propagated clocks, electrical limits, and all required mode/corner results.
Check your understanding
Questions to reason through.
What should you check before fixing negative slack?
Verify the clocks and generated clocks, modes, I/O delays, uncertainty, exceptions, case analysis, path grouping, and whether the reported startpoint and endpoint match architectural intent. Then inspect the full path and physical context. Optimizing a path created by a bad constraint wastes effort; cutting a real failing path hides a bug.
Put it into practice
Explain the decision behind the design.
- Pipeline a critical pathTrade architectural latency for shorter combinational depth.→
- Choose coupled timing ECOsImprove setup and hold without losing QoR or correctness.→
Complete the guide

