https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89785
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org,
| |redi at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I guess that is because potential_constant_expression_1 punts on THROW_EXPR.
There is some code to not recurse if e.g. IF_STMT or COND_EXPR condition
evaluates to constant zero or nonzero, but that is not the case here.
I actually don't know what in the standard requires something like
potential_constant_expression{,_1} rather than just punting during constexpr
evaluation if some non-constexpr construct is encountered. For the cases
listed in dcl.constexpr which may not show up in constexpr functions I thought
that is covered in the parser already.
