This is the mail archive of the
mailing list for the GCC project.
Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Andreas Jaeger <aj at suse dot de>, Jakub Jelinek <jakub at redhat dot com>,"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 09:03:46 -0400 (EDT)
- Subject: Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- Reply-to: dberlin at dberlin dot org
> |> > That's the same result as given on IA-32 or IA-64, but those
> |> > tests are
> |> > #if !defined __i386__ && !defined __ia64__
> |> > Guess at least __alpha__ is a good candidate for this treatment too.
> |> x86-64 has the same problem, everything passes except bitfield3 (this
> |> is with GCC 3.2 plus some extra patches),
> Same on s390x. Are there any platforms where it *does* pass?
I could swear I ran these tests on x86 or powerpc (can't remember which)
when it was first released by Intel, and everything passed.