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: Richard Henderson <rth at redhat dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 2 Aug 2002 15:23:17 -0700
- Subject: Re: C++ ABI testing issues, gcc-3.3 <-> gcc-3.2 compatibility
- References: <email@example.com>
On Fri, Aug 02, 2002 at 09:16:14AM -0700, Benjamin Kosnik wrote:
> (Brendan Kehoe, Jeff Law suggestion to run 'make check-c++' two ways,
> one with a new compiler and an old library, and the other with an old
> compiler and a new library, and look for testsuite regressions)
Indeed. For reference, what's the best way to do this?
What you want, I think, is to run the testsuite either
with an installed compiler or installed library, but I
thought the testsuite is set up to only look in the
current tree for both.
> 3.2 libstdc++.so.5 in a 3.3 build directory, make check == 0K
> 3.3 libstdc++.so.5 in a 3.2 build directory, make check == 15 FAILS
Ouch. This definitely needs to be investigated post haste.