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: Vtable incompatibility between GCC 3.0/3.2?

From: Joe Buck <jbuck at synopsys dot com>
To: Andreas Jaeger <aj at suse dot de>
Cc: Stephan Bergmann <stephan dot bergmann at sun dot com>, gcc at gcc dot gnu dot org
Date: Fri, 5 Sep 2003 09:21:39 -0700
Subject: Re: Vtable incompatibility between GCC 3.0/3.2?
References: <3F584E1E.2080308@sun.com> <u87k4n39a6.fsf@gromit.moeb> <3F5888B7.9030303@sun.com> <u8r82vs6m3.fsf@gromit.moeb>

On Fri, Sep 05, 2003 at 03:32:52PM +0200, Andreas Jaeger wrote:
> In a nutshell:
> 
> - 3.0 had old libstdc++
> 
> - 3.1 has new libstdc++
> 
> - 3.2 is ABI incompatible to earlier compilers
> 
> - 3.3 was expected to be compatible to 3.2 but a few days a bug was
>   found where 3.3 was not compatible to 3.2 (and not anymore to the
>   written ABI).

However, this bug is in a rather obscure corner case involving bitfields
and inheritance from a virtual base class.  It would be very hard to trip
over it.

References:
- Vtable incompatibility between GCC 3.0/3.2?
  - From: Stephan Bergmann
- Re: Vtable incompatibility between GCC 3.0/3.2?
  - From: Andreas Jaeger
- Re: Vtable incompatibility between GCC 3.0/3.2?
  - From: Stephan Bergmann
- Re: Vtable incompatibility between GCC 3.0/3.2?
  - From: Andreas Jaeger

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