Direct vs. Indirect Addressing Modes: Key Differences & Performance Impact
Direct addressing tells the CPU the exact memory cell to fetch data from; the address is embedded in the instruction. Indirect addressing gives the CPU a pointer: the instruction holds an address that itself points to the final data location.
Programmers mix them up because both use addresses—yet one is “go to room 302,” the other “go to the envelope that says where room 302 is.” Think of direct as GPS coordinates, indirect as a friend texting you directions.
Key Differences
Direct mode is faster (single memory access) but inflexible—data must stay in one spot. Indirect mode adds flexibility by allowing pointers and arrays at the cost of an extra memory read, slightly slowing execution.
Which One Should You Choose?
Choose direct for tight loops with fixed data—like reading sensor values. Choose indirect when data moves (linked lists, dynamic buffers) or when you need compact code that can reference many locations via one pointer.
Examples and Daily Life
Direct: “Pay $50 to account 1234.” Indirect: “Pay $50 to the account number written on this sticky note.” One is absolute; the other lets the note change without rewriting the payment form.
Does indirect always slow things down?
Not always; modern CPUs cache the extra read, so the penalty shrinks on repeated access.
Can I mix both modes in one program?
Yes—most compilers use direct for constants and indirect for variables, optimizing speed and flexibility together.