Leakage Recovery: Theory Deep Dive

Foundational theory

Leakage Recovery is a core part of Area, Power & Timing Tradeoffs. Leakage recovery replaces fast cells with higher-VT alternatives while preserving margin on critical paths and corners. Senior synthesis engineers connect every QoR claim to constraint context, compile setup, and reproducible artifacts.

Core concepts explained

• Leakage recovery replaces fast cells with higher-VT alternatives while preserving margin on critical paths and corners.

• Primary metric: leakage delta, WNS guardband consumed, swapped-cell count

• Primary artifact: leakage recovery report, swap list, hold/setup regression report

• Owners: power owner, synthesis owner, STA owner

• Compare timing, area, and power together

• Preserve run manifest for every regression jump

Why this matters at closure

At tapeout pace, Leakage Recovery decisions can either shorten closure loops or create hidden debt. PPA closure requires explicit tradeoff governance, not single-metric optimization.

Mental model

timing-safe cells
  -> swap to higher VT
  -> re-check setup/hold
  -> keep only safe swaps

Worked intuition

1. Freeze RTL tag, constraint tag, and compile switches.

2. Open leakage delta, WNS guardband consumed, swapped-cell count and isolate the first meaningful regression.

3. Classify whether issue is constraints, mapping transform, or physical estimate.

4. Collect leakage recovery report, swap list, hold/setup regression report and owner signoff evidence.

5. Pick minimal reversible fix and define rollback criteria.

6. Run timing + power + area regression matrix before merge.

Common misconceptions

• Better WNS always means better overall QoR.

• dont_touch is harmless if timing still passes.

• Retiming gain is free and always safe for formal.

• Topographical estimates are equivalent to signoff route outcomes.

Visual reinforcement

Leakage recovery pass

timing-safe cells
  -> swap to higher VT
  -> re-check setup/hold
  -> keep only safe swaps

Layer responsibilities

SYNTHESIS OWNERSHIP LAYERS — Leakage Recovery

layer               owns                          failure mode
----------------    ---------------------------   -------------------------
constraints         clocks/exceptions/policy      fake QoR optimism
mapping             cell choices/structure        depth/fanout regressions
optimization        timing/power tradeoffs        one-metric overfitting
physical-aware      topo/congestion estimates     handoff delta surprises
closure             ECO order/regression          fixes break other corners

Synthesis deep dive

PPA closure is a constrained tradeoff problem, not a timing-only exercise.

Concept diagram

PPA TRIAD

timing target <-> power budget <-> area cap

Metric 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.

Theory reinforcement

PPA closure requires explicit tradeoff governance, not single-metric optimization.