ECO, Retiming, and Clock-Gating Checks: Non-Equivalence Debug to Root Cause: Review Checklist

Review checklist

Review Checklist for ECO, Retiming, and Clock-Gating Checks: Non-Equivalence Debug to Root Cause is anchored on non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class. Convert outcomes into assumption-aware, evidence-backed actions.

• Requirement scope and risk tier are explicit.

• Assumption model is traceable and reviewed.

• Mechanism classification is evidence-backed.

• Owner, rollback trigger, and validation matrix are documented.

• Owners signed: formal verification owner, rtl owner, Equivalence Checking (LEC/SEC) owner.

Formal deep dive

Equivalence confidence comes from transformation-aware setup and rapid first-divergence diagnosis.

Concept diagram

EQUIVALENCE WORKFLOW

golden and revised design -> mapping and alignment -> mismatch triage -> closure evidence

Metric graph

LEC/SEC DEBUG SIGNALS

setup mismatches        █████
real behavioral deltas  ███
resolved divergences    ███████

Metrics and artifacts to collect

• compare-point match quality

• SEC latency-alignment success

• RTL-to-gate variant coverage

• ECO mismatch root-cause aging

Mini case study

A late ECO mismatch was traced to clock-gating setup, then closed with repeatable SEC alignment rules.

Debug branches

• Classify mismatch source before editing waiver sets.

• Use SEC when latency movement is intentional.

• Replay first divergence in simulation for cross-validation.

Senior review question

Ask: which requirement intent is proven, under which assumptions, and what residual risk remains?

Key takeaways

• Tie each proof claim to assumption boundaries and reachability evidence.

• Prefer minimal reversible fixes and preserve legal behavior visibility.

Common pitfalls

• Treating runtime reduction as proof-quality improvement without audits.

• Declaring closure while critical covers remain unreachable.

• Using broad waivers instead of first-divergence root-cause ownership.

Principal formal review addendum

ECO, Retiming, and Clock-Gating Checks: Non-Equivalence Debug to Root Cause should be reviewed as a requirement-evidence workflow, not a single status report.

Use non-vacuous closure rate, counterexample turnaround time, and requirement-level residual risk trend as the monitoring lens and formal closure packet: assumptions audit, proof status matrix, counterexample classification, and requirement traceability as closure proof.

Equivalence closure quality depends on transformation-aware setup and first-divergence debug discipline. Strong teams preserve legal reachability while improving convergence.