RTL-to-Gate LEC: Post-Synthesis Signoff and Constraint Hygiene: Interview Drills

Interview drills

Interview Drills for RTL-to-Gate LEC: Post-Synthesis Signoff and Constraint Hygiene is anchored on non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class. Convert outcomes into assumption-aware, evidence-backed actions.

PROMPT
You observe regression in non-vacuous closure rate, counterexample turnaround, and residual-risk trend by requirement class for RTL-to-Gate LEC: Post-Synthesis Signoff and Constraint Hygiene. Explain root cause and signoff decision.

STRONG ANSWER
1. Defines requirement context and first divergence.
2. Explains mechanism: RTL-to-gate LEC is a standard synthesis signoff gate that verifies implementation netlists preserve RTL intent after logic optimization, technology mapping, and library insertion.
3. Requests proving artifact: closure packet for RTL-to-Gate LEC: Post-Synthesis Signoff and Constraint Hygiene: assumptions audit, proof status matrix, and replay-ready divergence trace
4. Proposes bounded fix + owner + rollback-safe validation.

WEAK ANSWER
Gives generic formal advice without model boundaries, proof quality, or ownership.

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

RTL-to-Gate LEC: Post-Synthesis Signoff and Constraint Hygiene 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.