diff options
| author | Jason Merrill <jason@redhat.com> | 2020-05-05 17:39:19 -0400 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2020-05-05 17:39:31 -0400 |
| commit | 04b89192ace3a766a17374d5bef8fb19d9be2d7c (patch) | |
| tree | 5311f78e69d7c223b1fbbee8f33d64a0f3a351f3 /gcc/combine.c | |
| parent | d0aed8d5ba77e0756f3c9ebcd65eba1bfb11f24b (diff) | |
| download | gcc-04b89192ace3a766a17374d5bef8fb19d9be2d7c.zip gcc-04b89192ace3a766a17374d5bef8fb19d9be2d7c.tar.gz gcc-04b89192ace3a766a17374d5bef8fb19d9be2d7c.tar.bz2 | |
c++: constexpr and lambda capture [PR90212]
This is the same issue as PR86429, just in potential_constant_expression_1
rather than cxx_eval_constant_expression. As in that case, when we're
trying to evaluate a constant expression within a lambda, we don't have a
constant closure object to refer to, but we can try to refer directly to the
captured variable.
gcc/cp/ChangeLog
2020-05-05 Jason Merrill <jason@redhat.com>
PR c++/90212
* constexpr.c (potential_constant_expression_1): In a lambda
function, consider a captured variable directly.
Diffstat (limited to 'gcc/combine.c')
0 files changed, 0 insertions, 0 deletions