https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94600
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Hans-Peter Nilsson <h...@gcc.gnu.org>: https://gcc.gnu.org/g:ac2347289d4d8000a078b540b6c9c2c74bb33471 commit r10-9121-gac2347289d4d8000a078b540b6c9c2c74bb33471 Author: Hans-Peter Nilsson <h...@axis.com> Date: Fri Dec 4 20:27:23 2020 +0100 doc/implement-c.texi: About same-as-scalar-type volatile aggregate accesses, PR94600 We say very little about reads and writes to aggregate / compound objects, just scalar objects (i.e. assignments don't cause reads). Let's lets say something safe about aggregate objects, but only for those that are the same size as a scalar type. There's an equal-sounding section (Volatiles) in extend.texi, but this seems a more appropriate place, as specifying the behavior of a standard qualifier. gcc: 2020-12-04 Hans-Peter Nilsson <h...@axis.com> Martin Sebor <mse...@redhat.com> PR middle-end/94600 * doc/implement-c.texi (Qualifiers implementation): Add blurb about access to the whole of a volatile aggregate object, only for same-size as a scalar object. (cherry picked from commit eb79f4db49c5f5a807555e9d374524664eb537bf)
