aboutsummaryrefslogtreecommitdiff
path: root/ABOUT-NLS
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2020-12-04 20:27:23 +0100
committerHans-Peter Nilsson <hp@axis.com>2020-12-04 20:29:27 +0100
commiteb79f4db49c5f5a807555e9d374524664eb537bf (patch)
tree21d2016631f24ef996758f88fbdc631e4bb9848e /ABOUT-NLS
parent78c4a9feceaccf487516aa1eff417e0741556e10 (diff)
downloadgcc-eb79f4db49c5f5a807555e9d374524664eb537bf.zip
gcc-eb79f4db49c5f5a807555e9d374524664eb537bf.tar.gz
gcc-eb79f4db49c5f5a807555e9d374524664eb537bf.tar.bz2
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 <hp@axis.com> Martin Sebor <msebor@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.
Diffstat (limited to 'ABOUT-NLS')
0 files changed, 0 insertions, 0 deletions