DWidening the instruction register to accommodate the additional opcodes
In hardwired control, control signals are generated by combinational logic circuits (AND/OR gates, decoders, state machines) that directly map opcode + state → control signals. Adding instructions means changing this logic network, re-verifying that all timing constraints are met, and possibly altering the physical layout. This is exactly what makes hardwired control inflexible. By contrast, a microprogrammed design would simply require writing new microcode — a software-like change with no hardware modification needed.
Question 2 Multiple Choice
Why does microprogrammed control generally have higher execution latency than hardwired control for the same instruction?
AMicroprogrammed processors must run at a lower clock frequency to ensure correct microinstruction sequencing
BThe control store must be refreshed every cycle, adding a mandatory pipeline stall
CGenerating control signals requires reading microinstructions from memory on each step, whereas hardwired logic produces signals through direct gate propagation
DMicroprogrammed processors cannot overlap instruction fetch with decode
In microprogrammed control, each step of instruction execution requires fetching a microinstruction from the control store (a ROM or PLA) and reading its bits to drive the datapath. This memory access adds latency. In hardwired control, the mapping from opcode to control signals is 'burned into' the circuit — signals propagate through a few gate delays with no memory lookup. The memory access in microprogrammed control is fast by modern standards, but it is still slower than direct combinational logic.
Question 3 True / False
Microcode is the low-level assembly language that systems programmers write to control hardware directly.
TTrue
FFalse
Answer: False
Microcode is internal CPU control logic stored in a control store ROM inside the processor. It is invisible to programmers — it operates below the ISA level and cannot be directly read or written by software (in most architectures). Machine code (and assembly language) operates at the ISA level: load, store, add, branch. Microcode operates one level below, controlling individual datapath signals on each clock cycle. Both hardwired and microprogrammed processors execute the same machine-code ISA; the difference is only in how the CPU implements each instruction internally.
Question 4 True / False
A hardwired control unit and a microprogrammed control unit can implement exactly the same instruction set architecture; the programmer-visible behavior is identical regardless of which implementation is used.
TTrue
FFalse
Answer: True
The ISA is the interface between software and hardware — it defines what instructions exist, their encoding, and their visible effects on registers and memory. The control unit is an implementation detail below that interface. Whether control signals are generated by combinational logic (hardwired) or by stepping through microcode (microprogrammed), the programmer-visible behavior is identical. This is a fundamental principle of computer architecture: the ISA abstracts away implementation details.
Question 5 Short Answer
Why do modern x86 processors use a hybrid approach — hardwired fast paths for common instructions and microcode for complex ones — rather than committing to one approach exclusively?
Think about your answer, then reveal below.
Model answer: Hardwired control is fast (signals from direct gate logic, no memory lookup) but inflexible — adding instructions requires redesigning hardware. Microprogrammed control is flexible (new instructions require only new microcode) but slower. Modern x86 defines hundreds of instructions, including many complex, rarely-used operations. A pure hardwired design would be nearly impossible to extend over decades; a pure microprogrammed design would impose microcode-lookup overhead on even the simplest instructions. The hybrid optimizes the common case with hardwired paths while retaining the flexibility of microcode for complex or rare instructions.
This hybrid design reflects the general principle of optimizing for the common case. It also explains how x86 has absorbed new instruction set extensions (MMX, SSE, AVX) for 40+ years without complete redesigns — new instructions go into microcode, while the most performance-critical core instructions remain hardwired. The same tradeoff appears throughout computer architecture: specialization for the frequent case, generality for the rare case.