diff options
| author | Jason Merrill <jason@redhat.com> | 2025-03-05 16:42:32 -0500 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2025-04-21 15:43:54 -0400 |
| commit | e6ae0de72ef696c4016cc66c53a4aa49a1e900a6 (patch) | |
| tree | e6db20ccf0758d29c0a286cef207f0cd37204b0e /libjava/java/util/BitSet.java | |
| parent | 0907a810f586b07636cc5b83dba6025eb5240655 (diff) | |
| download | gcc-e6ae0de72ef696c4016cc66c53a4aa49a1e900a6.zip gcc-e6ae0de72ef696c4016cc66c53a4aa49a1e900a6.tar.gz gcc-e6ae0de72ef696c4016cc66c53a4aa49a1e900a6.tar.bz2 | |
c++: static constexpr strictness [PR99456]
r11-7740 limited constexpr rejection of conversion from pointer to integer
to manifestly constant-evaluated contexts; it should instead check whether
we're in strict mode.
The comment for that commit noted that making this change regressed other
tests, which turned out to be because maybe_constant_init_1 was not being
properly strict for variables declared constexpr/constinit.
PR c++/99456
gcc/cp/ChangeLog:
* constexpr.cc (cxx_eval_constant_expression): Check strict
instead of manifestly_const_eval.
(maybe_constant_init_1): Be strict for static constexpr vars.
Diffstat (limited to 'libjava/java/util/BitSet.java')
0 files changed, 0 insertions, 0 deletions