diff options
author | Jason Merrill <jason@redhat.com> | 2023-03-23 15:57:39 -0400 |
---|---|---|
committer | Jason Merrill <jason@redhat.com> | 2023-03-28 11:26:03 -0400 |
commit | 0e8fc610fb7112deb8c33c673a52983368dde9b7 (patch) | |
tree | deaa252b7d72c7ef6414e4a4089ebca4017b5256 /libjava/testsuite/libjava.lang/initexc.java | |
parent | 5a923516ae61ddc6dd863891db13189cbf392411 (diff) | |
download | gcc-0e8fc610fb7112deb8c33c673a52983368dde9b7.zip gcc-0e8fc610fb7112deb8c33c673a52983368dde9b7.tar.gz gcc-0e8fc610fb7112deb8c33c673a52983368dde9b7.tar.bz2 |
c-family: -Wsequence-point and COMPONENT_REF [PR107163]
The patch for PR91415 fixed -Wsequence-point to treat shifts and ARRAY_REF
as sequenced in C++17, and COMPONENT_REF as well. But this is unnecessary
for COMPONENT_REF, since the RHS is just a FIELD_DECL with no actual
evaluation, and in this testcase handling COMPONENT_REF as sequenced blows
up fast in a deep inheritance tree. Instead, look through it.
PR c++/107163
gcc/c-family/ChangeLog:
* c-common.cc (verify_tree): Don't use sequenced handling
for COMPONENT_REF.
gcc/testsuite/ChangeLog:
* g++.dg/warn/Wsequence-point-5.C: New test.
Diffstat (limited to 'libjava/testsuite/libjava.lang/initexc.java')
0 files changed, 0 insertions, 0 deletions