Why not extend the language with an "rmem" keyword or function that you use like this: rmem(pointer) and you're guaranteed to produce a memory read, rather than

Why not extend the language with an "rmem" keyword or function that you use like this: rmem(pointer) and you're guaranteed to produce a memory read, rather than reusing a value in register. Then say that the compiler is free to assume two pointers/arrays etc. never overlap. Then, introduce linters which can detect most cases of these-two-pointers-might-overlap. Maybe runtime ones like valgrind. I want to write C as high level assembly. If I put values in registers and reuse them, then I'm opening myself for the same kind of problems as if I'm writing C and not doing explicit memory reads.