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
    • Synthesis Flow Overview
    • Synthesizable RTL and Inference
    • Reading Netlists and Reports
      • Cell Counts from stat
      • Area by Cell Type
      • Hierarchy, Fanout and Net Names
      • Longest Path, Write and Read Back
  • Logic Optimisation and Mapping20
  • 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

‹Reading Netlists and Reports
  1. Topics
  2. Logic Synthesis
  3. Synthesis Foundations
  4. Reading Netlists and Reports
  5. Cell Counts from stat

Part 1 · Synthesis Foundations · Intermediate

Cell Counts from stat

Read a stat report: cell counts by type, wires, and what each line answers.

On this page

    What stat prints

    stat reports how many cells of each type the design holds. It also reports the wire count, which covers ports and internal nets together.

    Run it on the generic netlist to see the tool-neutral structure, and again after mapping to see library cells. The block below is an illustrative layout, numbers invented for this lesson.

    Diagram
    illustrative layout, numbers invented for this lesson (an example slice, never tool output):
    cells: NAND2 12, NOR2 4, INV 6, DFF 8
    total cells = 12 + 4 + 6 + 8 = 30
    wires = 41 (stated with the layout)

    Cells, wires and pins

    Three nouns carry every report. A cell is one gate or flop instance, a wire is one net, and a pin is one connection point on a cell.

    Term

    Meaning

    Cell

    One instance of a gate or flop, counted under its type.

    Wire (net)

    One named connection: a port or an internal net.

    Pin

    One terminal of a cell, such as an input or an output.

    Port

    A wire that crosses the module boundary.

    A checked three-gate example

    The design below ANDs two pairs and ORs the results. Its script pins every number the lesson quotes: two $and cells, one $or cell and three gates in total.

    yosys
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    read_verilog <<EOV
    module top(input a, b, c, d, output y);
    wire n1, n2;
    assign n1 = a & b;
    assign n2 = c & d;
    assign y = n1 | n2;
    endmodule
    EOV
    hierarchy -check -top top
    select -assert-count 2 t:$and
    select -assert-count 1 t:$or
    select -assert-count 3 t:$and t:$or %u
    stat
    log PASS: three gates elaborate as written

    Three gates implement the function: two ANDs feeding one OR.

    Common mistakes

    Common pitfall

    A single total cell count hides the mix. Always read the by-type breakdown before deciding what to resize or restructure.

    Interview

    Likely probes: reading a by-type table, and wires against cells.

    • Cells by type say what was built; the total alone says almost nothing.

    • The script pins two $and, one $or and three gates in total through one union selection.

    • stat on the generic netlist shows structure; stat -liberty after mapping shows area.

    Check yourself stat reports two $and cells and one $or cell. How many gates is that, and what does the union selection add?

    Three gates: two ANDs feeding one OR. The union selection pins that total in one assertion.

    Check yourself A report total says 30 cells but shows no by-type breakdown. Why is that total hard to act on?

    The total hides which cells dominate. Without the by-type split, there is nothing to resize or restructure.

    Related topics

    • Area by cell type

    • Cell Libraries and Liberty

    Previous

    13 / 139

    Next: Area by Cell Type

    Up next

    Up nextArea by Cell Type

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Hierarchy, Fanout and Net Names
    • Longest Path, Write and Read Back