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 testing issues, gcc-3.3 <-> gcc-3.2 compatibility

From: Jakub Jelinek <jakub at redhat dot com>
To: Andreas Jaeger <aj at suse dot de>
Cc: "Goodman, Joe" <joe dot goodman at intel dot com>, bkoz at redhat dot com, gcc at gcc dot gnu dot org, rth at redhat dot com
Date: Mon, 5 Aug 2002 13:22:54 +0200
Subject: Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
References: <D9223EB959A5D511A98F00508B68C20C10AFDC61@orsmsx108.jf.intel.com> <u8r8hdiycy.fsf@gromit.moeb> <u8ptwxft53.fsf@gromit.moeb>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Mon, Aug 05, 2002 at 01:21:28PM +0200, Andreas Jaeger wrote:
> Andreas Jaeger <aj@suse.de> writes:
> 
> > I'll test 3.3 later, I first have to bootstrap it without checking due
> > to the problems in the x86 backend.  I'll send a report after that.
> 
> GCC 3.3 has the same problems - and removing
> -DUSE_FUNCTION_DESCRIPTORS fixed the two vtable bugs that I had.

BTW: I've fixed the bitfield1.C bug, testing ATM.
But there is another problem - alignment of __m64 fields in records.

	Jakub

References:
- RE: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
  - From: Goodman, Joe
- Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
  - From: Andreas Jaeger
- Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
  - From: Andreas Jaeger

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