https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116634

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Jason Merrill
<ja...@gcc.gnu.org>:

https://gcc.gnu.org/g:ce25ca4da198ebc269d41ee6a9ac880ae8f67ad6

commit r14-10887-gce25ca4da198ebc269d41ee6a9ac880ae8f67ad6
Author: Jason Merrill <ja...@redhat.com>
Date:   Mon Nov 4 17:48:46 2024 -0500

    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.

    (cherry picked from commit 3545aab00152ed3db1d7ce6ca4e1671dde276980)

Reply via email to