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: Andreas Schwab <schwab at suse dot de>
- To: dberlin at dberlin dot org
- 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, 05 Aug 2002 15:06:24 +0200
- Subject: Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- References: <Pine.LNX.email@example.com>
Daniel Berlin <firstname.lastname@example.org> writes:
|> > |> > 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.
On x86 it is explicitly disabled.
Andreas Schwab, SuSE Labs, email@example.com
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."