https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109868
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 55092 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55092&action=edit gcc14-pr109868.patch I think the FE shouldn't initialize those, rather than gimplifier fixing it up later. In fact, I think we shouldn't initialize any unnamed bitfields, but am not changing that, because zero initialization is supposed to clear all padding bytes and !CONSTRUCTOR_NO_CLEARING certainly doesn't guarantee that in the middle-end, I think we need some other CONSTRUCTOR flag and middle-end assurance that the padding bits are then cleared.
