Home / Learn / Computer Architecture & Logic

🔌 Computer Architecture & Logic

From transistors to pipelines. 51 topics, from beginner to advanced.

Computer architecture explains how hardware runs software. Starting from logic gates and binary arithmetic, this area moves up through the CPU datapath, instruction pipelines, caches and memory hierarchy. Knowing these layers helps explain why some code runs thousands of times faster than other code that does the same work.

Who this area is for

Students of electrical engineering and computer engineering, software developers who want to understand performance, and anyone curious about how a processor runs their code.

Real-world use cases

Explaining why accessing data sequentially in memory is much faster than random access.
Designing a simple arithmetic circuit from logic gates.
Reasoning about how branch mispredictions slow down a tight loop.
Understanding why a loop over a large array is faster when it reads memory in order.
Choosing a data type that wastes no bits in an embedded device with little memory.

Topics in Computer Architecture & Logic

Beginner (17)

Binary Number System — Base-2 representation using only digits 0 and 1.
Hexadecimal and Octal — Compact base-16 and base-8 notations for binary data.
Two's Complement — Standard encoding of signed integers in binary.
Floating Point Representation — Scientific-notation style encoding of real numbers in bits.
Character Encoding — Mapping characters to numeric codes such as ASCII and Unicode.
Logic Gates — Basic circuits implementing AND, OR, NOT and related functions.
Truth Tables — Exhaustive listings of outputs for every input combination.
Boolean Algebra — Algebra of true and false values with laws for simplification.
Karnaugh Maps — Graphical method for minimizing Boolean expressions.
Combinational Circuits — Circuits whose outputs depend only on current inputs.
Adders — Circuits performing binary addition with carry.
Multiplexers — Circuits selecting one of many inputs using control lines.
Flip-Flops — One-bit memory elements that store state on a clock edge.
Registers — Small fast storage locations inside the processor.
Clock Signal — Periodic pulse synchronizing sequential logic.
Von Neumann Architecture — Design storing instructions and data in the same memory.
Fetch-Decode-Execute Cycle — The repeated instruction processing loop of a CPU.

Intermediate (17)

Sequential Circuits — Circuits whose outputs depend on current inputs and stored state.
Finite State Machines in Hardware — Hardware controllers moving between defined states.
Arithmetic Logic Unit — CPU component performing arithmetic and bitwise operations.
Instruction Set Architecture — The contract between software and processor hardware.
RISC vs CISC — Philosophies of simple fixed instructions versus rich complex ones.
Assembly Language — Human-readable mnemonics for machine instructions.
Addressing Modes — Ways instructions specify operand locations.
Memory Hierarchy — Tiers of storage trading speed for capacity.
Cache Memory — Small fast memory holding recently used data close to the CPU.
Cache Mapping — Direct, set-associative and fully associative placement policies.
Cache Replacement Policies — Rules like LRU deciding which block to evict.
Virtual Memory in Hardware — Address translation giving each process a private space.
TLB — Cache of recent virtual-to-physical address translations.
Instruction Pipelining — Overlapping stages of multiple instructions.
Pipeline Hazards — Data, control and structural conflicts that stall pipelines.
Branch Prediction — Guessing branch outcomes to keep the pipeline full.
Out-of-Order Execution — Running instructions as operands become ready rather than program order.

Advanced (17)

Superscalar Processors — CPUs issuing multiple instructions per cycle.
Speculative Execution — Executing ahead on predicted paths and discarding if wrong.
Multicore Processors — Chips with several independent processing cores.
Cache Coherence — Keeping copies of shared data consistent across cores.
SIMD and Vector Processing — Applying one instruction to many data elements at once.
GPU Architecture — Massively parallel processors for throughput workloads.
DMA — Hardware letting devices move data without CPU involvement.
Interrupts — Signals diverting the CPU to handle urgent events.
Bus Architecture — Shared pathways carrying data, address and control signals.
Storage Devices — HDDs and SSDs and how they persist data.
RAID — Combining disks for redundancy or performance.
Memory Consistency Models — Rules on the apparent order of memory operations across cores.
Microarchitecture Side Channels — Leaks exploiting timing and cache behavior of CPUs.
FPGA — Reconfigurable chips programmed to implement custom hardware.
Hardware Description Languages — Languages like Verilog describing digital circuits.
ARM and RISC-V — Prominent modern reduced instruction set families.
Moore's Law and Dennard Scaling — Historical trends in transistor density and power.

How to study Computer Architecture & Logic

Build the ideas up from the bottom: learn number systems, then gates, then registers and memory, and only then the pipeline. Draw each circuit or diagram by hand. The Visual Lab binary and logic-gate views let you test each idea against a truth table.

Frequently asked questions

What is a CPU cache and why does it matter?

A cache is a small, fast memory close to the CPU that stores recently used data. Programs that reuse nearby data run much faster because they hit the cache more often.

What is pipelining?

Pipelining splits instruction execution into stages, such as fetch, decode and execute, so several instructions overlap. It raises throughput without making any single instruction faster.

Do I need to know logic gates to be a programmer?

Not to write most software, but understanding gates and binary explains integer overflow, bit manipulation and how a computer turns instructions into electrical signals.

Do I need to know hardware to be a software developer?

Not to start, but the basics of memory, caches and pipelines explain many performance problems. Developers who understand them write code that runs faster without guesswork.

What is the difference between architecture and organization?

Architecture is what the processor exposes to software, such as its instruction set. Organization is how the hardware implements it, such as the pipeline depth or cache size.

Open the interactive Computer Architecture & Logic area Take the Computer Architecture & Logic quiz