diff options
| author | Patrick Palka <ppalka@redhat.com> | 2023-03-16 14:47:43 -0400 |
|---|---|---|
| committer | Patrick Palka <ppalka@redhat.com> | 2023-03-16 14:47:43 -0400 |
| commit | 31cdfdef04701e10cffcec4578b2337684f0e4bc (patch) | |
| tree | 81e471cb3f4b83772bfb63559f433e5908f3049e /gcc/function.h | |
| parent | c630157fd01140dbce120c1409c413a97dc17104 (diff) | |
| download | gcc-31cdfdef04701e10cffcec4578b2337684f0e4bc.zip gcc-31cdfdef04701e10cffcec4578b2337684f0e4bc.tar.gz gcc-31cdfdef04701e10cffcec4578b2337684f0e4bc.tar.bz2 | |
c++: maybe_constant_init and unevaluated operands [PR109030]
This testcase in this PR (already fixed by r13-6526-ge4692319fd5fc7)
demonstrates that maybe_constant_init can be called on an unevaluated
operand (e.g. from massage_init_elt) so this entry point should also
limit constant evaluation in that case, like maybe_constant_value does.
PR c++/109030
gcc/cp/ChangeLog:
* constexpr.cc (maybe_constant_init_1): For an unevaluated
non-manifestly-constant operand, don't constant evaluate
and instead call fold_to_constant as in maybe_constant_value.
gcc/testsuite/ChangeLog:
* g++.dg/cpp2a/constexpr-inst2.C: New test.
Diffstat (limited to 'gcc/function.h')
0 files changed, 0 insertions, 0 deletions