The Z80 — Design Philosophy: Richness and Compatibility

Chapters 2–4 covered the 6502 end to end. This chapter opens an identical three-chapter arc for the Z80 — design philosophy first, exactly as cpu8bit1-2 did — so the two chips stay genuinely comparable rather than lopsided. And the contrast starts immediately: where the 6502 was built by a team that left one company to chase a price target from a clean slate, the Z80 was built by a designer extending his own earlier work, under a completely different kind of constraint.

The Team Behind the Chip — Federico Faggin's Break From Intel

Federico Faggin had already helped design the Intel 4004, 8008, and — directly relevant here — the 8080 itself, before leaving Intel in 1974 to found Zilog alongside Ralph Ungermann. The Z80, released in 1976, wasn't Faggin encountering the 8080 as an outside competitor the way MOS Technology approached the market — it was its own original co-designer building a deliberate successor to it.

Built to Be a Superset — What "Compatible" Actually Meant

cpu8bit1-1's own Exercise 2 already touched this at a high level; here's the full picture. The Z80 was designed so that any existing 8080 machine code would run on it completely unchanged — while adding a substantial layer of new registers, instructions, and addressing modes on top. This produces a fundamentally different starting position than the 6502's own:

• The 6502 team could freely decide "we don't need this" — nothing existing constrained them, since they were designing from a genuine blank slate.
• The Z80 team could only add. Every instruction and register the 8080 already had needed to keep working exactly as before, whether or not it was still the cleanest way to do something — new capability had to be layered on top of that existing foundation, never used to replace or simplify it.

The CISC-Leaning Richness — Concrete Consequences

That compatibility mandate shows up as real, measurable richness once the 8080's own instruction set becomes the Z80's starting point rather than its ceiling:

• More instructions — the 8080 offered roughly 78 instruction types; the Z80, built as its superset, is commonly cited as offering around 158 — roughly double, all while remaining fully compatible with the original 78.
• More registers — a genuine shadow register set and dedicated index registers, both entirely new, covered in full in cpu8bit1-6.
• More addressing modes — covered in cpu8bit1-7.

Fitting roughly double the instructions into a design that still had to decode the 8080's original 256-opcode space required a real engineering trick: the Z80 reserves four special prefix bytes — CB, DD, ED, and FD — each one signaling "the next byte selects from an entirely separate table of additional instructions." It's a genuinely clever escape hatch, extending the instruction space far beyond what a single unprefixed byte could ever address — engineering cleverness aimed squarely at capability, the mirror image of the 6502's own cleverness aimed at cost.

Contrasted Directly With the 6502's Minimalism

Notice the transistor count moves in exactly the direction each chip's own founding constraint predicts: the 6502's cost target pushed it down, the Z80's added capability pushed it up — roughly double the 6502's own budget. Both chips are still answering the same underlying question cpu8bit1-2 raised — what does the transistor budget actually buy you — just pointed in opposite directions by two genuinely different starting pressures.

Hands-On Exercises