https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69482
--- Comment #6 from wipedout at yandex dot ru --- The explanations sound reasonable so far. Yet I expect that this problem will be reported again and again because WOW A SECURITY HOLE so perhaps it'd be reasonable to change gcc behavior so that when source code contains writes through volatile pointers then the variable overwritten is actually allocated in memory and writes are emitted. That would make machine code emitted more predictable.
