[Bug c++/90432] [9/10 Regression] Internal compiler error with no_unique_address empty type with constructor call followed by value initialized to non-zero

[cvs-commit at gcc dot gnu.org]

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

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

https://gcc.gnu.org/g:9af9e004831f8efdfb68c2affea07b17fadd3279

commit r9-8332-g9af9e004831f8efdfb68c2affea07b17fadd3279
Author: Jason Merrill <ja...@redhat.com>
Date:   Wed Mar 4 17:30:58 2020 -0500

    c++: Fix [[no_unique_address]] and default mem-init [PR90432]

    output_constructor doesn't like two consecutive entries with fields at the
    same position; let's avoid adding the one for the empty field.

    gcc/cp/ChangeLog
    2020-03-04  Jason Merrill  <ja...@redhat.com>

        PR c++/90432
        * init.c (perform_member_init): Don't do aggregate initialization of
        empty field.
        * constexpr.c (cx_check_missing_mem_inits): Don't enforce
        initialization of empty field.