aboutsummaryrefslogtreecommitdiff
path: root/libgcc
diff options
context:
space:
mode:
authorIain Sandoe <iain@sandoe.co.uk>2020-06-01 08:28:35 +0100
committerIain Sandoe <iain@sandoe.co.uk>2020-06-01 19:44:22 +0100
commit88f48e2967ead9be262483618238efa9c7c842ec (patch)
tree5f5e2d58a9ba4ceba801ad7913dbfb8163d080c1 /libgcc
parent118158b646d402b0fb5d760e4827611b731fe6f3 (diff)
downloadgcc-88f48e2967ead9be262483618238efa9c7c842ec.zip
gcc-88f48e2967ead9be262483618238efa9c7c842ec.tar.gz
gcc-88f48e2967ead9be262483618238efa9c7c842ec.tar.bz2
coroutines: Correct handling of references in parm copies [PR95350].
Adjust to handle rvalue refs the same way as clang, and to correct the handling of moves when a copy CTOR is present. This is one area where we could make things easier for the end-user (as was implemented before this change), however there needs to be agreement about when the full statement containing a coroutine call ends (i.e. when the ramp terminates or when the coroutine terminates). gcc/cp/ChangeLog: PR c++/95350 * coroutines.cc (struct param_info): Remove rv_ref field. (build_actor_fn): Remove specifial rvalue ref handling. (morph_fn_to_coro): Likewise. gcc/testsuite/ChangeLog: PR c++/95350 * g++.dg/coroutines/torture/func-params-08.C: Adjust test to reflect that all rvalue refs are dangling. * g++.dg/coroutines/torture/func-params-09-awaitable-parms.C: Likewise. * g++.dg/coroutines/pr95350.C: New test.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions