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: Nathan Sidwell <nathan at acm dot org>
- To: dberlin at dberlin dot org
- Cc: Andreas Schwab <schwab at suse dot de>, Andreas Jaeger <aj at suse dot de>, Jakub Jelinek <jakub at redhat dot com>, "Goodman, Joe" <joe dot goodman at intel dot com>, bkoz <bkoz at redhat dot com>, gcc <gcc at gcc dot gnu dot org>, rth <rth at redhat dot com>
- Date: Mon, 05 Aug 2002 14:06:23 +0100
- Subject: Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- References: <Pine.LNX.firstname.lastname@example.org>
- Reply-to: nathan at compsci dot bristol dot ac dot uk
Daniel Berlin wrote:
> > |> > 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.
ditto, and the same this morning with the 3.2 branch. I'm confused.
Dr Nathan Sidwell :: Computer Science Department :: Bristol University
The voices in my head told me to say this
email@example.com http://www.cs.bris.ac.uk/~nathan/ firstname.lastname@example.org