Where Is a Pointer Variable’s Own Address Stored?

For a local variable, the compiler commonly gives it an offset relative to the current stack frame or stack pointer. Conceptually, it might generate something like “load the value at frame pointer plus 8.” If p is moved into a register, the CPU can use that register directly. Registers are small storage locations inside the CPU, so they do not need ordinary memory addresses.

You can create pointers to pointers if you need them: for example, an int ** can point to a variable that stores an int *. But that is an explicit data structure, not something required for every pointer. Eventually the chain ends because the program's instructions, registers, and known address calculations provide the starting point.

A pointer is just another variable whose value happens to be interpreted as a memory address. If x is at address 2000, p might be stored at address 1000, with the number 2000 stored in those bytes. The computer does not need another pointer to find p: the compiler or runtime already knows where p is, often through a fixed location, a stack-frame offset, or a register.

The stack and heap are common places for variables, but the important idea is that a pointer is not a magical connection. It is usually just an integer-sized value representing an address. Dereferencing p tells the CPU to use the address stored in p and access the memory there. The exact address of p may change between executions, which is why compilers often use relative offsets or relocation rather than hard-coding it.