diff options
| author | Jason Merrill <jason@redhat.com> | 2024-11-04 17:48:46 -0500 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2024-11-05 11:02:36 -0500 |
| commit | 3545aab00152ed3db1d7ce6ca4e1671dde276980 (patch) | |
| tree | 2fa9c16b10f74c7c8f6993cad9f37f6d9401cc70 /gcc/fortran/error.cc | |
| parent | 6543a214485c0a722152e34de37424f9a0104bbb (diff) | |
| download | gcc-3545aab00152ed3db1d7ce6ca4e1671dde276980.zip gcc-3545aab00152ed3db1d7ce6ca4e1671dde276980.tar.gz gcc-3545aab00152ed3db1d7ce6ca4e1671dde276980.tar.bz2 | |
c++: allow array mem-init with -fpermissive [PR116634]
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.
Diffstat (limited to 'gcc/fortran/error.cc')
0 files changed, 0 insertions, 0 deletions