This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ ABI Issues
- From: "David O'Brien" <obrien at FreeBSD dot org>
- To: Allan Sandfeld Jensen <snowwolf at one2one-networks dot com>
- Cc: gcc at gcc dot gnu dot org, Mark Mitchell <mark at codesourcery dot com>
- Date: Sat, 7 Sep 2002 13:32:39 -0700
- Subject: Re: C++ ABI Issues
- Organization: The NUXI BSD Group
- References: <27170000.1030400196@warlock.codesourcery.com> <3D6B71A4.2328715@codesourcery.com> <200208271457.58862.snowwolf@one2one-networks.com>
- Reply-to: obrien at FreeBSD dot org
On Tue, Aug 27, 2002 at 02:57:58PM +0200, Allan Sandfeld Jensen wrote:
> Since 3.3 has to stay compatible with 3.2, the 3.2 ABI will most likely have
> to stay default.
WHY?? 3.2->3.3 is a major version release, so ABI changes are allowed.
For FreeBSD we would like to see all known C++ ABI bugs fixed in 3.3.0.
It is not too late for us to move from 3.2 -> 3.3. In fact we've had so
many problems with our update to 3.2 from 3.1-prerelease that we may have
to go to 3.3 anyway.
The proposals for a switch to choose the C++ ABI sound excellent to
FreeBSD. I don't care if the default ABI is the 3.2 one, or the "bug
free" one -- I can easily set what we want in config/freebsd-specs.h.
A -Wabi in 3.2.1 would also be well received by FreeBSD as we can use
that to help decided if we should move to 3.3 for our 5.0 release.