diff options
author | Marek Polacek <polacek@redhat.com> | 2024-07-17 15:44:26 -0400 |
---|---|---|
committer | Marek Polacek <polacek@redhat.com> | 2024-07-31 08:49:53 -0400 |
commit | bbc9c0423ca754e8e6ff80e08948ff52986337a0 (patch) | |
tree | 213957be23fb2063a9a66eb50c00fa20c14d8fe1 /gcc/dwarf2codeview.cc | |
parent | f40fd85c32c9ab4849065d0d14cd5a7ad67619b8 (diff) | |
download | gcc-bbc9c0423ca754e8e6ff80e08948ff52986337a0.zip gcc-bbc9c0423ca754e8e6ff80e08948ff52986337a0.tar.gz gcc-bbc9c0423ca754e8e6ff80e08948ff52986337a0.tar.bz2 |
c++: array new with value-initialization, again [PR115645]
Unfortunately, my r15-1946 fix broke the attached testcase; the
constexpr evaluation reported an error about not being able to
evaluate the code emitted by build_vec_init. Jason figured out
it's because we were wrongly setting try_const to false, where
in fact it should have been true. Value-initialization of scalars
is constexpr, so we should check that alongside of
type_has_constexpr_default_constructor.
PR c++/115645
gcc/cp/ChangeLog:
* init.cc (build_vec_init): When initializing a scalar type, try to
create a constant initializer.
gcc/testsuite/ChangeLog:
* g++.dg/cpp2a/constexpr-new23.C: New test.
Diffstat (limited to 'gcc/dwarf2codeview.cc')
0 files changed, 0 insertions, 0 deletions