diff options
| author | Iain Sandoe <iain@sandoe.co.uk> | 2020-06-10 00:15:28 +0100 |
|---|---|---|
| committer | Giuliano Belinassi <giuliano.belinassi@usp.br> | 2020-08-17 13:11:51 -0300 |
| commit | ce6914411cd7d4133f829aae6dcea01069c69fc5 (patch) | |
| tree | ad176dd9778b3da350486aef41286e45d10f7acb /gcc/fortran/expr.c | |
| parent | 43addc0c6b7537007b088cf44f1a7520dee0f1d9 (diff) | |
| download | gcc-ce6914411cd7d4133f829aae6dcea01069c69fc5.zip gcc-ce6914411cd7d4133f829aae6dcea01069c69fc5.tar.gz gcc-ce6914411cd7d4133f829aae6dcea01069c69fc5.tar.bz2 | |
coroutines: Make call argument handling more robust [PR95440]
build_new_method_call is supposed to be able to handle a null
arguments list pointer (when the method has no parms). There
were a couple of places where uses of the argument list pointer
were not defended against NULL.
gcc/cp/ChangeLog:
PR c++/95440
* call.c (add_candidates): Use vec_safe_length() for
testing the arguments list.
(build_new_method_call_1): Use vec_safe_is_empty() when
checking for an empty args list.
gcc/testsuite/ChangeLog:
PR c++/95440
* g++.dg/coroutines/pr95440.C: New test.
Diffstat (limited to 'gcc/fortran/expr.c')
0 files changed, 0 insertions, 0 deletions