Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • Logic Synthesis Glossary
  • Logic Synthesis Cheatsheet
  • Synthesis Foundations14
  • Logic Optimisation and Mapping20
  • Constraints and Timing15
  • Sequential, FSM and Memory19
  • Datapath Synthesis14
  • Area, Power and Test14
  • Verification, ECO and Handoff15
    • Equivalence Checking
    • Incremental Compile and ECO
      • Re-run or Patch
      • Logic Cone Isolation
      • ECO Netlist Edits
      • Hierarchy and dont_touch
      • Equivalence and QoR Regression
    • Physical-Aware Synthesis and Handoff
  • Flows and Debugging15
  • Interview and Judgment11
Loading lesson

‹Verification, ECO and Handoff
  1. Topics
  2. Logic Synthesis
  3. Verification, ECO and Handoff
  4. Incremental Compile and ECO

Part 7 · Verification, ECO and Handoff · Intermediate

Incremental Compile and ECO

Re-run versus patch, spare cells, and keeping equivalence through an ECO.

  • 5topics
  • 5lessons

Late RTL changes rarely justify a full re-run. Incremental compile re-optimises the affected cone, and an ECO patches the netlist with spare cells and rewiring, with equivalence re-proven after every patch.

Decision flow from RTL change to re-proof.
A change that fits one cone is patched, otherwise the flow re-runs, and both paths end in proof.

Lesson

What it covers

Re-run or Patch

When a late change needs a full re-run and when a patch is enough.

Logic Cone Isolation

Finding the cone of a changed output with a runnable Python model.

ECO Netlist Edits

Spare cells, rewiring, and resizing, with Yosys count checks over disjoint cones.

Hierarchy and dont_touch

How preserved boundaries trade stability against quality of results.

Equivalence and QoR Regression

Re-proving equivalence after an ECO and checking QoR guardbands.

Check yourself When is a full re-run the right call instead of an ECO?

When the change spreads beyond one cone, when spare cells run out, or when QoR after the patch misses the target the full flow would meet.

Interview

Carry one sentence per lesson: patch inside one cone and re-run outside it, cones are found by backward fanin walk, ECO edits use spare cells and rewiring, preserved boundaries buy stability at some QoR cost, and every patch ends with proof plus a QoR check.

Related topics

  • Up: Verification, ECO and Handoff

  • Previous: Equivalence Checking

  • Next: Physical-Aware Synthesis and Handoff

PreviousNext: Re-run or Patch

Up next

Up nextRe-run or Patch

Sign in to save progress

Practice this lessonReport an error

See also

  • Equivalence Checking
  • Physical-Aware Synthesis and Handoff