This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- From: Andreas Jaeger <aj at suse dot de>
- To: "Goodman, Joe" <joe dot goodman at intel dot com>
- Cc: bkoz at redhat dot com, gcc at gcc dot gnu dot org, rth at redhat dot com
- Date: Mon, 05 Aug 2002 09:00:29 +0200
- Subject: Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- References: <D9223EB959A5D511A98F00508B68C20C10AFDC61@orsmsx108.jf.intel.com>
"Goodman, Joe" <joe.goodman@intel.com> writes:
> We provide a C++ ABI test suite you can download from
> http://developer.intel.com/software/products/opensource/. Please feel free
> to download and run this suite.
Thanks for reminding us. I did test it some weeks ago and decided to
look again add it - and noticed that I configured it wrong the last
time and was not executing the tests (config.mk disables them by
default on non-ia64 platforms :-( ).
Here're the results on i686-linux-gnu from GCC 3.2 branch as of
2002-08-04:
./bitfield1
Test 1 Failure: bitfield1.cpp:59
./dynamic1
Test 9 Failure: dynamic1.cpp:79
./virtual3
Test 4 Failure: virtual3.cpp:65
./virtual9
Test 9 Failure: virtual9.cpp:92
./vtable1
Test 3 Failure: vtable1.cpp:70
./vtable2
Test 3 Failure: vtable2.cpp:102
And the known failure for new (we have size_t == int on
i686-linux-gnu):
missing: _Znwm
missing: _Znam
make: *** [operator1.pass] Error 1
Note that the testsuite aborts after the first error, there might be
more errors - but it's not possible to figure this out right now.
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.
I don't know whether those failures are critical or not. Has anybody
looked into these already?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj