News for hackers. Stuff that matters.
Re:Torvalds: Standards need to be questioned by kazinator on Wednesday June 06, 2018 @08:27AM (#17246456)
"access" refers to reading there. Not reading or writing. Objects may be treated as arrays of character type to the extent that their value may be examined that way.

If you memcpy a uint64_t to a double, the implementation is not required to notice that the double variable's value has changed; a subsequent access to that variable can continue to refer to a register. It's not a matter of what bit pattern was stored there.

Re:Torvalds: Standards need to be questioned by comex on Wednesday June 06, 2018 @04:13PM (#17250680)
No, "access" is defined as reading or writing:

> 3.1 > 1 access >〈execution-time action〉 to read or modify the value of an object

Thus, the requirement is symmetrical. The compiler must consider any char write as potentially aliasing a subsequent read (or write) of any type, unless it can prove non-aliasing without depending on type. And similarly, it must consider a write of any type as potentially aliasing a subsequent char read/write.