This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: C++ ABI Issues


I wrote:

> | It seems that even if it does, we can preserve libstdc++'s binary
> | compatibility by adding a dummy field that exactly fills up any padding.

Gaby writes:
> Isn't this the compiler should be doing (with appropriate flags if
> necessary)?  It certainly does know where to fill things.  I would
> certainly prefer that to clutering V3 with pad0, pad1, ...

How could we do that?  We'd have to either tell the compiler somehow which
classes to compile in the old way and which classes to compile in the new
way, or else use the 3.2 ABI for everything, forever.

In practice, we may be lucky and not need to do anything at all.  Let's
reopen this one when we have some data.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]