https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81140
Bug ID: 81140
Summary: Update docs to reflect P0612R0: clarify meaning of
"volatile access" + that it includes any glvalue
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: db0451 at gmail dot com
Target Milestone: ---
As far as I can tell, according to P0162R0: NB comment CH 2
http://open-std.org/JTC1/SC22/WG21/docs/papers/2017/p0612r0.html
which was adopted earlier this year:
https://isocpp.org/blog/2017/03/2017-03-post-kona-mailing-available
the established, implementation-defined behaviour of g++ is now Standard
behaviour in C++ (if not C).
If so, then I guess this section of the documentation needs updated:
7.1 When is a Volatile C++ Object Accessed?
https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Volatiles.html
I don't know whether this is intended as a DR to be backported to older
standards; my Standard-foo is not that strong.
