> Sides, actually, because both compile time and run time tend to be stacks. Actually, runtime does not use a stack in the relevant sense (on non-toy compilers

> Sides, actually, because both compile time and run time tend to be stacks. Actually, runtime does not use a stack in the relevant sense (on non-toy compilers anyway). It allocates a stack frame on the call stack on a per-function basis, with possibly some other bits to handle variable-length arrays, but the actual local variables are allocated inside the stack frame in mostly the same way they're allocated in registers (but with less spilling). So the same 'undeclare'/register-coloring semantics apply.