Synthesis & Logic Optimization · All levels
Leakage Recovery: Worked Example
Worked Example for Leakage Recovery.
Worked example
Worked Example for Leakage Recovery focuses on leakage delta, WNS guardband consumed, swapped-cell count. The goal is to connect observed QoR movement to mechanism, ownership, and regression risk.
A weekly compile reports leakage delta, WNS guardband consumed, swapped-cell count regression. Instead of random knob tuning, start by proving whether input context changed and which mechanism dominates.
Sequence under inspection
SYNTHESIS FLOW — Leakage Recovery
RTL + constraints
|
v
elaboration + checks
|
v
mapping + optimization
|
v
QoR reports (timing/area/power)
|
v
incremental ECO + regression
Primary metric: leakage delta, WNS guardband consumed, swapped-cell countLeakage recovery pass
timing-safe cells
-> swap to higher VT
-> re-check setup/hold
-> keep only safe swapsCapture baseline and regressed artifact pair.
Confirm manifest parity (RTL, SDC, libs, switches).
Pin first metric drift and mechanism hypothesis.
Reproduce with leakage recovery report, swap list, hold/setup regression report.
Apply one reversible fix and run matrix regression.
Did the fix hold?
BEFORE / AFTER QOR — Leakage Recovery
QoR score
0 | --- target zone
-1 | ● regression
-2 | ● baseline
-0.5| ● after fix
+----------------------------------> iteration
Validate timing + area + power, not one number.Synthesis deep dive
PPA closure is a constrained tradeoff problem, not a timing-only exercise.
Concept diagram
PPA TRIAD
timing target <-> power budget <-> area capMetric graph
PARETO PROGRESSION
early runs o o
balanced point o
over-tuned o (risk)Reports and artifacts
VT mix
leakage trend
dynamic power trend
PPA Pareto table
Mini case study
LVT-heavy fix recovered setup but violated leakage target; balanced VT strategy closed both.
Debug branches
Timing-only claims need power check
Validate hold on VT swaps
Use Pareto memo
Senior review question
Ask: what evidence proves this QoR move is real and stable?
Key takeaways
State exact run context (RTL, SDC, libs, switches) with every QoR claim.
Re-run timing, area, and power regressions after each synthesis ECO.
Common pitfalls
Comparing runs with mismatched constraints or library views.
Timing-only fixes that violate power or area budgets.
Skipping equivalence checks after structural changes.
Principal synthesis review addendum
Leakage recovery replaces fast cells with higher-VT alternatives while preserving margin on critical paths and corners.
Metric: leakage delta, WNS guardband consumed, swapped-cell count