What is RISC, how does it differ from CISC, and why did Arm succeed?
Short answer: RISC (Reduced Instruction Set Computer) uses a small set of simple, fixed-length instructions, each doing one thing, with memory accessed only by explicit load and store instructions and many general-purpose registers. CISC (Complex Instruction Set Computer, e.g. x86) has many variable-length instructions, some doing a lot of work and operating directly on memory. RISC makes the hardware simpler, easier to pipeline and more power-efficient, which is why Arm became dominant in phones and embedded systems.
| RISC (Arm, RISC-V) | CISC (x86) | |
|---|---|---|
| Instruction length | fixed (32-bit A64; 16/32-bit Thumb-2) | variable (1–15 bytes on x86) |
| Memory access | only load/store instructions | most instructions can use memory operands |
| Registers | many (16 in AArch32, 31 in AArch64) | fewer architectural registers historically |
| Decode | simple, cheap | complex; modern x86 decodes into internal RISC-like micro-ops |
| Code density | lower (helped by Thumb, compressed RISC-V) | higher |
| Power/area | lower | higher |
Why it mattered for Arm: Arm's original 1985 design (from Acorn, for the BBC Micro's successor) aimed to bring workstation-class performance to low-cost machines, often summarised as "MIPS for the masses" (MIPS here meaning millions of instructions per second). The simple RISC design needed few transistors, which turned out to make it very power efficient, almost as a side effect. When mobile and battery-powered devices took off, low power per instruction became the most valuable property, and Arm's licensing model (selling designs, not chips) let many companies build Arm SoCs.
Modern reality: the distinction has blurred: x86 cores internally execute RISC-like micro-operations, and Arm added complex instructions (SIMD, crypto, atomics). Energy efficiency now depends more on microarchitecture than on the instruction set label, but the clean load/store design still makes Arm cores smaller and simpler, which matters most at the low end (Cortex-M).
Follow-up: "What is Thumb?" A compressed instruction set with 16-bit encodings (Thumb-2 mixes 16- and 32-bit) for better code density; Cortex-M executes only Thumb.