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

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • Logic Synthesis Glossary
  • Logic Synthesis Cheatsheet
  • Synthesis Foundations14
  • Logic Optimisation and Mapping20
    • Boolean Optimisation
    • Technology Mapping
    • Cell Libraries and Liberty
    • Structuring and Buffering
      • Fanout, Slew and Capacitance Rules
      • Delay of a Driver with Load
      • Buffer Trees
      • Sizing, Cloning and Restructuring
      • Fanout Constraints in Practice
  • Constraints and Timing15
  • Sequential, FSM and Memory19
  • Datapath Synthesis14
  • Area, Power and Test14
  • Verification, ECO and Handoff15
  • Flows and Debugging15
  • Interview and Judgment11
Loading lesson

←Logic Optimisation and Mapping
  1. Topics
  2. Logic Synthesis
  3. Logic Optimisation and Mapping
  4. Structuring and Buffering

Part 2 of 9Part 2 of 9/Logic Optimisation and MappingIntermediate

Structuring and Buffering

Fanout, slew and capacitance rules and how synthesis repairs them.

  • 5topics
  • 5lessons

Every overloaded driver ends in the same loop: check the rules, repair, recheck. Without the loop, teams fix the violation they see and ship the one the repair created.

After this lesson you can: name the four repairs for an overloaded driver and run the check-repair-recheck loop in order.

Large fanouts slow drivers and break slew and capacitance limits. Synthesis repairs them with buffer trees, gate sizing, cloning and restructuring, trading area for rules that must hold.

Term

Meaning

Fanout

The number of sinks one driver feeds. Large fanout means large load.

Slew (transition)

How fast a signal edge rises or falls. Heavy loads stretch edges out.

Capacitance load

Wire plus pin capacitance the driver must charge. It sets delay and slew.

Buffer tree

Staged buffers that split one large fanout into small, legal steps.

Cloning

Duplicating a driver so each copy feeds fewer sinks.

Repair loop for an overloaded driver: check rules, repair violations, recheck, then close timing.
The commercial repair loop: check the three design rules, repair any violation, recheck, then fix timing. No recorded run below sets a rule limit, so every repair shown is delay- and load-driven; the loop states the commercial flow, not a recorded one.

What you can do after this topic: read the three design rules off a library and a constraint file, predict how delay moves with load, size a buffer tree with ceiling division, tell sizing from cloning from restructuring, and price a fanout repair in area before you ask for it. The worked tree on the buffer-trees page stages 64 sinks at branch 4, in groups of 16, 4 and 1.

Lesson

What it covers

Fanout, Slew and Capacitance Rules

Library and constraint rules, load units on the shared net, and a recorded load comparison.

Delay of a Driver with Load

A linear delay model fitted to the real NAND2 table, checked in Python.

Buffer Trees

Ceiling-division stage counts, a 64-flop shared net, the mapper's recorded repair, and the branch-width optimum.

Sizing, Cloning and Restructuring

X1/X2/X4 choices from a recorded sweep, hand-priced cloning input load, and restructuring for depth.

Fanout Constraints in Practice

The measured cost of repair: area against fanout, load and target.

Check yourself A net drives 64 sinks through 3 stages of branch-4 buffers. How many buffers does the tree hold?

21 buffers: 16 in the first stage, 4 in the second and 1 in the last. Each stage divides the remaining load by 4.

Carry one sentence per lesson: rules cap load units, slew and load; delay rises with load in pF; trees split fanout with ceiling division; sizing, cloning and restructuring trade area for speed; repairs cost area that grows with fanout and load.

  • Buffer trees, sizing, cloning and restructuring all trade area for rules that must hold.

  • Design-rule repairs run before timing optimisation, not beside it.

Rule of thumb: check the rules, repair, then recheck before closing timing.

How this was checked

This hub page runs no tools itself. Its repair loop states the commercial flow; the five lessons below record only the delay- and load-driven part of it, since no run sets a design-rule limit. All runs use Yosys 0.69 and ABC against the teaching library sized.lib and are recorded by the course checker (scripts/tools/run-rtl-testbenches.mjs with COURSE=synth).

  • Interview: run a mock interview on this topic

PreviousNext: Fanout, Slew and Capacitance Rules

Up next

Up nextFanout, Slew and Capacitance Rules

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Boolean Optimisation
  • Technology Mapping
  • Cell Libraries and Liberty