diff options
author | Jonathan Wakely <jwakely@redhat.com> | 2020-09-22 08:42:18 +0100 |
---|---|---|
committer | Jonathan Wakely <jwakely@redhat.com> | 2020-09-22 08:42:18 +0100 |
commit | 7825399092d572ce8ea82c4aa8dfeb65076b0e52 (patch) | |
tree | b67e14910d10e7fde6844489ceaf9915876b99bf /gcc/expmed.h | |
parent | d149962d6ac3c940fee95707cb6bafdb055e9bea (diff) | |
download | gcc-7825399092d572ce8ea82c4aa8dfeb65076b0e52.zip gcc-7825399092d572ce8ea82c4aa8dfeb65076b0e52.tar.gz gcc-7825399092d572ce8ea82c4aa8dfeb65076b0e52.tar.bz2 |
libstdc++: Use correct argument type for __use_alloc, again [PR 96803]
While backporting 5494edae83ad33c769bd1ebc98f0c492453a6417 I noticed
that it's still not correct. I made the allocator-extended constructor
use the right type for the uses-allocator construction detection, but I
used an rvalue when it should be a const lvalue.
This should fix it properly this time.
libstdc++-v3/ChangeLog:
PR libstdc++/96803
* include/std/tuple
(_Tuple_impl(allocator_arg_t, Alloc, const _Tuple_impl<U...>&)):
Use correct value category in __use_alloc call.
* testsuite/20_util/tuple/cons/96803.cc: Check with constructors
that require correct value category to be used.
Diffstat (limited to 'gcc/expmed.h')
0 files changed, 0 insertions, 0 deletions