https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127382
--- Comment #15 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 16 Sep 2026, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127382 > > --- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > (In reply to [email protected] from comment #13) > > That means when we store to _BitInt we can put garbage in the padding > > as we are properly extending at loads? That is, memory is not part > > of the ABI and an application does not have to adhere to padding > > details for its memory representation? > > Only on x86, aarch64 and powerpc*. On other _BitInt targets it can skip the > extension on loads and has to extend before stores. > Memory (at least addressable memory which escaped or could have otherwise the > padding bits inspected) is part of the ABI. Interesting times for portable applications and their storage formats then ... is there sth like __builtin_extend_bitint (_BitInt(N) *) that can be used to massage the padding into target required form?
