diff options
| author | Jason Merrill <jason@redhat.com> | 2024-11-04 17:48:46 -0500 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2024-11-05 12:31:19 -0500 |
| commit | ce25ca4da198ebc269d41ee6a9ac880ae8f67ad6 (patch) | |
| tree | 9104d7e12c98be1df16b79e90b789112733a17c7 /gcc/cppmain.c | |
| parent | c16e4ecd8fdc2230a313fe795333fa97652ba19f (diff) | |
| download | gcc-releases/gcc-14.zip gcc-releases/gcc-14.tar.gz gcc-releases/gcc-14.tar.bz2 | |
c++: allow array mem-init with -fpermissive [PR116634]releases/gcc-14
We've accidentally accepted this forever (at least as far back as 4.7), but
it's always been ill-formed; this was PR59465. And we didn't accept it for
scalar types. But rather than switch to a hard error for this code, let's
give a permerror so affected code can continue to work with -fpermissive.
PR c++/116634
gcc/cp/ChangeLog:
* init.cc (can_init_array_with_p): Allow PR59465 case with
permerror.
gcc/testsuite/ChangeLog:
* g++.dg/diagnostic/aggr-init1.C: Expect warning with -fpermissive.
* g++.dg/init/array62.C: Adjust diagnostic.
* g++.dg/init/array63.C: Adjust diagnostic.
* g++.dg/init/array64.C: Adjust diagnostic.
(cherry picked from commit 3545aab00152ed3db1d7ce6ca4e1671dde276980)
Diffstat (limited to 'gcc/cppmain.c')
0 files changed, 0 insertions, 0 deletions