diff options
author | Marek Polacek <polacek@redhat.com> | 2024-07-02 15:22:39 -0400 |
---|---|---|
committer | Marek Polacek <polacek@redhat.com> | 2024-07-10 12:34:14 -0400 |
commit | fde96e8205f343e6471a11cc9def967bb5dd5362 (patch) | |
tree | 009f3a2f04e7b22b825a2c102eb0588f974f6e8f /gcc/c/c-decl.cc | |
parent | 9d20529d94b23275885f380d155fe8671ab5353a (diff) | |
download | gcc-fde96e8205f343e6471a11cc9def967bb5dd5362.zip gcc-fde96e8205f343e6471a11cc9def967bb5dd5362.tar.gz gcc-fde96e8205f343e6471a11cc9def967bb5dd5362.tar.bz2 |
c++: array new with value-initialization [PR115645]
This extends the r11-5179 fix which doesn't work with multidimensional
arrays. In particular,
struct S {
explicit S() { }
};
auto p = new S[1][1]();
should not say "converting to S from initializer list would use
explicit constructor" because there's no {}. However, since we
went into the block where we create a {}, we got confused. We
should not have gotten there but we did because array_p was true.
This patch refines the check once more.
PR c++/115645
gcc/cp/ChangeLog:
* init.cc (build_new): Don't do any deduction for arrays with
bounds if it's value-initialized.
gcc/testsuite/ChangeLog:
* g++.dg/expr/anew7.C: New test.
Diffstat (limited to 'gcc/c/c-decl.cc')
0 files changed, 0 insertions, 0 deletions