Leakage Recovery: Expanded Case Study

Extended case study

Closure review: leakage delta, WNS guardband consumed, swapped-cell count regressed after a change touching Leakage Recovery.

Background

Team previously had stable baseline across weekly compile runs and agreed guardbands.

Symptoms observed

• leakage delta, WNS guardband consumed, swapped-cell count moved beyond threshold

• Mismatch between local and CI runs

• Owner disagreement on first fix

Investigation timeline

1. Hour 0: freeze manifests and compare run metadata

2. Hour 1: isolate section/topic-specific failure pattern

3. Hour 2: verify constraints and library view consistency

4. Hour 3: inspect transform and mapping deltas

5. Hour 4: choose one reversible fix

6. Hour 5: execute full regression matrix

7. Hour 6: publish closure memo and next actions

Root cause

Root cause centered on Leakage Recovery: Leakage recovery replaces fast cells with higher-VT alternatives while preserving margin on critical paths and corners.

Fix and validation

• Targeted synthesis tweak with audit trail

• Re-run leakage recovery report, swap list, hold/setup regression report

• Update dashboard and handoff notes

Lessons learned

• Compare like-for-like runs only

• Assign clear owner before ECO

• Keep rollback ready

CASE STUDY — Leakage Recovery
baseline / regression / recovery QoR snapshot

Sequence under stress

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 count

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.

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