aboutsummaryrefslogtreecommitdiff
path: root/libcpp
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2022-08-16 13:15:32 +0200
committerJakub Jelinek <jakub@redhat.com>2022-08-16 13:15:32 +0200
commit6e790ca4615443fa395ac5cdba1ab6c87810985c (patch)
tree00ceed0766b075550459790275efcfde267a9f05 /libcpp
parente56b695aa3aed3c0c80616bba569bbeb4a06b5e5 (diff)
downloadgcc-6e790ca4615443fa395ac5cdba1ab6c87810985c.zip
gcc-6e790ca4615443fa395ac5cdba1ab6c87810985c.tar.gz
gcc-6e790ca4615443fa395ac5cdba1ab6c87810985c.tar.bz2
c++: Implement P2327R1 - De-deprecating volatile compound operations
From what I can see, this has been voted in as a DR and as it means we warn less often than before in -std={gnu,c}++2{0,3} modes or with -Wvolatile, I wonder if it shouldn't be backported to affected release branches as well. 2022-08-16 Jakub Jelinek <jakub@redhat.com> * typeck.cc (cp_build_modify_expr): Implement P2327R1 - De-deprecating volatile compound operations. Don't warn for |=, &= or ^= with volatile lhs. * expr.cc (mark_use) <case MODIFY_EXPR>: Adjust warning wording, leave out simple. * g++.dg/cpp2a/volatile1.C: Adjust for de-deprecation of volatile compound |=, &= and ^= operations. * g++.dg/cpp2a/volatile3.C: Likewise. * g++.dg/cpp2a/volatile5.C: Likewise.
Diffstat (limited to 'libcpp')
0 files changed, 0 insertions, 0 deletions