https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117016
Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> ---
Thank you for taking the time to report this inefficiency. But this is working
as intended. The design goal of the fixed_size ABI was an ABI-stable "this is
never going to break on ABI boundaries" type. The only way to guarantee that
without an oracle that can predict the future is to use the most conservative
alignment.
FWIW, I always thought that fixed_size is an interesting experiment and
potentially an ABI tag someone at some point might want. But I don't think it
should have been the prominent "I want a fixed number of elements" ABI that it
is in the TS. This is going to be better with C++26 ... if we make it. :)
