diff options
| author | Jason Merrill <jason@redhat.com> | 2024-09-15 13:50:04 +0200 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2024-09-18 08:58:52 -0400 |
| commit | 8733d5d3873977d6ca82d71b28728650f988e9c8 (patch) | |
| tree | 1430a816602f810b813da7b2599a91f7a5a41f78 /gcc/tree-vectorizer.h | |
| parent | 6f3b6a451771cd54c98768e7db3c5d58aab2b6aa (diff) | |
| download | gcc-8733d5d3873977d6ca82d71b28728650f988e9c8.zip gcc-8733d5d3873977d6ca82d71b28728650f988e9c8.tar.gz gcc-8733d5d3873977d6ca82d71b28728650f988e9c8.tar.bz2 | |
c++: -Wdangling-reference and empty class [PR115361]
We can't have a dangling reference to an empty class unless it's
specifically to that class or one of its bases. This was giving a
false positive on the _ExtractKey pattern in libstdc++ hashtable.h.
This also adjusts the order of arguments to reference_related_p, which
is relevant for empty classes (unlike scalars).
Several of the classes in the testsuite needed to gain data members to
continue to warn.
PR c++/115361
gcc/cp/ChangeLog:
* call.cc (do_warn_dangling_reference): Check is_empty_class.
gcc/testsuite/ChangeLog:
* g++.dg/ext/attr-no-dangling6.C
* g++.dg/ext/attr-no-dangling7.C
* g++.dg/ext/attr-no-dangling8.C
* g++.dg/ext/attr-no-dangling9.C
* g++.dg/warn/Wdangling-reference1.C
* g++.dg/warn/Wdangling-reference2.C
* g++.dg/warn/Wdangling-reference3.C: Make classes non-empty.
* g++.dg/warn/Wdangling-reference23.C: New test.
Diffstat (limited to 'gcc/tree-vectorizer.h')
0 files changed, 0 insertions, 0 deletions