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 sym

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.