diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2021-10-12 15:09:50 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2021-10-12 16:05:15 +0100 |
| commit | 7481021364e75ba583972e15ed421a53988368ea (patch) | |
| tree | 153fe85eed952f390dc504d9e5982e48f25da0bb /gcc/dwarf2ctf.c | |
| parent | d9dfd7ad3e0196f60a3fc6df6d65a40fb905409f (diff) | |
| download | gcc-7481021364e75ba583972e15ed421a53988368ea.zip gcc-7481021364e75ba583972e15ed421a53988368ea.tar.gz gcc-7481021364e75ba583972e15ed421a53988368ea.tar.bz2 | |
libstdc++: Fix move construction of std::tuple with array elements [PR101960]
The r12-3022 commit only fixed the case where an array is the last
element of the tuple. This fixes the other cases too. We can just define
the move constructor as defaulted, which does the right thing. Changing
the move constructor to be trivial would be an ABI break, but since the
last base class still has a non-trivial move constructor, defining the
derived ones as defaulted doesn't change anything.
libstdc++-v3/ChangeLog:
PR libstdc++/101960
* include/std/tuple (_Tuple_impl(_Tuple_impl&&)): Define as
defauled.
* testsuite/20_util/tuple/cons/101960.cc: Check tuples with
array elements before the last element.
Diffstat (limited to 'gcc/dwarf2ctf.c')
0 files changed, 0 insertions, 0 deletions