This is the mail archive of the
mailing list for the GCC project.
Re: [cxx-abi-dev] Re: C++ ABI: Reuse of tail padding
- From: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
- To: Nathan Sidwell <nathan at codesourcery dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, cxx-abi-dev at codesourcery dot com, gcc at gcc dot gnu dot org, jason at redhat dot com
- Date: 15 Aug 2002 01:03:49 +0200
- Subject: Re: [cxx-abi-dev] Re: C++ ABI: Reuse of tail padding
- Organization: CMLA, ENS Cachan -- CNRS UMR 8536 (France)
- References: <firstname.lastname@example.org> <3D5AC85B.8E510A5A@codesourcery.com>
Nathan Sidwell <email@example.com> writes:
| > I think I would prefer to change G++, and drop this idea from the spec,
| > even though it is an optimization.
| Although using tail padding is neat, how many bytes would it
| save in real programs? You only get it with structs of the form
| int i;
| char c;
| or (on some non-i86 machines)
| double d;
| int i;
Right. However, I'm not sure if is about neat features (seriously).
People seeking for efficient space use are advised to declare
their data-members in (preferably decreasing) monotonic order of
alignment requirements. For those people, I think the principle of
least surprise should be honored if possible.