A commercial synthesis tool covers the same concepts but may iterate, merge, or reorder steps under different command names. Its reports differ in layout while carrying the same content: cells, counts, area, and timing.
Nothing in this topic is commercial-tool syntax. Command names here are Yosys passes, and constraint sketches are labelled illustrative.
Tool | Role in this course |
|---|---|
Yosys with ABC | The runnable tool: elaboration, optimisation, mapping, and reporting on small designs. |
Tool-neutral flow | The five-stage model by concept, so each idea transfers across tools. |
Python models | Small programs that check the arithmetic behind reports and tradeoffs. |
Yosys behaviour is described only where it is certain. Pass names such as proc, opt, techmap, abc, and stat are the vocabulary.
A number from a runnable block is backed by an assertion in that block. A wrong number fails the run, so the text can quote it safely.
Anything else is labelled where it stands: illustrative sketches say illustrative, and EXAMPLE parameters carry units with substituted values. Invented reports never pose as tool output.
The five-stage model, the input-output contract, and the constraint tradeoffs. Only the Yosys pass names stay behind.
As illustrative. Only asserted runnable output may be quoted as tool behaviour.