[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
gcc-bugzilla@gcc.gnu.org
Wed Mar 4 22:33:00 GMT 2020
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90432
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:6876b269bc7fe6465fedfed87c31e6175992129f
commit r10-7031-g6876b269bc7fe6465fedfed87c31e6175992129f
Author: Jason Merrill <jason@redhat.com>
Date: Wed Mar 4 12:08:42 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 <jason@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.
More information about the Gcc-bugs
mailing list