https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118070
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The libgcc problem actually doesn't exist, we could force all loads and stores from SSO marked _BitInts and their bitfields into native endianity temporaries if one would need to pass those to libgcc. But the rest still applies, we'd need to define what the other endianity _BitInt ABI is for each target supporting _BitInt. And given that different architectures can have different _BitInt layout ABIs, SSO wouldn't really achieve data exchangeability between those.
