ECO Netlist Patches: Review Checklist

Review checklist

Review Checklist for ECO Netlist Patches focuses on patch count, setup/hold recovery, patch-induced side effects. The goal is to connect observed QoR movement to mechanism, ownership, and regression risk.

• Run manifest is attached (RTL/SDC/libs/switches).

• Primary metric and impacted lane are named.

• Mechanism hypothesis is evidence-backed.

• Fix is reversible and owner-assigned.

• Regression matrix includes timing, area, power, and equivalence as needed.

• Owners signed: synthesis owner, STA owner, formal owner.

Sign-off ownership

OWNERSHIP MAP — ECO Netlist Patches

artifact              owner
----------------      -----------------
compile owner       synthesis owner
timing/power owner  STA owner
cross-team review   formal owner

Every QoR movement needs a named owner before ECO.

Synthesis deep dive

Incremental and ECO synthesis protect schedule only with strict regression discipline.

Concept diagram

INCREMENTAL ECO LOOP

identify delta -> localized compile -> patch -> regression -> release

Metric graph

ECO CYCLE TIME

full compile      ███████████
incremental       █████

Reports and artifacts

• incremental reuse

• ECO patch list

• LEC status

• regression matrix

Mini case study

Localized compile cut turnaround 40%, but skipped LEC caused rollback.

Debug branches

• Reuse ratio is not enough

• Patch locality check

• Always include equivalence hooks

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

ECO patching edits gate-level logic for urgent fixes; patch quality depends on locality, observability, and verification closure.

Metric: patch count, setup/hold recovery, patch-induced side effects