This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/14353] New: libstdc++ wchar tests run for -mabi=32
- From: "billingd at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Mar 2004 00:47:11 -0000
- Subject: [Bug libstdc++/14353] New: libstdc++ wchar tests run for -mabi=32
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
This is not a regression, as -mabi=32 support is new to 3.4
I have just enabled testing of the -o32 ABI on my irix6.5 testsuite runs
for gcc-3.4 and gcc-3.5.
See http://gcc.gnu.org/ml/gcc-testresults/2004-02/msg01329.html for an example.
Most of the libstdc++ testsuite failures are due to the absence of
wchar support in the -o32 ABI. Is there a way to disable of XFAIL
these tests for only one of the three ABI under test?
Phil Edwards [phil@codesourcery.com] says:
If wchar isn't supported, then configure should be turning it off. If it
isn't, then there will be a zero-length objdir/testsuite/testsuite_wchar_t
file indicating that the wchar tests should be run.
I see that:
- libstdc++-v3/testsuite/testsuite_wchar_t exists
- libstdc++-v3/mabi=64/testsuite/testsuite_wchar_t exists
- libstdc++-v3/mabi=32/testsuite/testsuite_wchar_t doesn't exist
which is correct, but the tests are still run for mabi=32.
This points to a test harness issue.
--
Summary: libstdc++ wchar tests run for -mabi=32
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: billingd at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: mips-sgi-irix6.5
GCC host triplet: mips-sgi-irix6.5
GCC target triplet: mips-sgi-irix6.5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14353