This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Binary Compatibility [was Re: libstdc++ compatibility]
- To: egcs at cygnus dot com
- Subject: Binary Compatibility [was Re: libstdc++ compatibility]
- From: Brendan Kehoe <brendan at cygnus dot com>
- Date: 22 Oct 1998 18:40:03 -0700
- Cc: brendan at cygnus dot com
- References: <Pine.LNX.4.04.9810181406440.2394-100000@alien.devel.redhat.com> <20275.908739682.cygnus.egcs@hurl.cygnus.com>
> The question in my mind is how can we test this functionality? Just being
> able to build the old library isn't enough, we have to verify to some extent
> that it is compatible with the old one.
>
> We've also got to get a handle on when we actually make incompatible changes.
> We've started thinking about that some, but not enough IMHO.
>
> Thoughts anyone?
On my ``Do This Soon'' list is the idea of putting together a suite of tests
that do testing of binary compatibility in g++. It'd include things like
check object layout, different pieces of symbol mangling, exception handling
layout, RTTI, virtual function calling & tables, etc etc. This seemed like a
great time to drop the question out for comment.
Does anyone have any ideas on how such a thing might be put together? The
goal would be to make it easier to catch binary incompatibilities when they're
introduced, rather than waiting (unconsciously) until a user bumps into 'em.
This is particularly the case as -fnew-abi continues to grow & expand.
Thoughts? Ideas?
B
--
Brendan Kehoe brendan@cygnus.com
Cygnus Solutions, Sunnyvale, CA +1 408 542 9600
Web page: http://www.zen.org/~brendan/