> To really learn about the innerworkings of the CPU, you must read a book about...the innerworkings of a CPU. But C doesn't map to the "inner workings of the

> To really learn about the innerworkings of the CPU, you must read a book about...the innerworkings of a CPU. But C doesn't map to the "inner workings of the CPU", it maps to a certain abstract machine, defined in the C standard [1]. If you think that C maps to an actual CPU, you're already using C wrong, and it probably shows – in the form of undefined behavior bugs. [1] standards, actually, pick your preferred version