This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Compiler timeouts in the basic_string tests
- From: Matt Austern <austern at apple dot com>
- To: libstdc++ at gcc dot gnu dot org, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Mon, 22 Dec 2003 11:31:41 -0800
- Subject: Compiler timeouts in the basic_string tests
Has anyone other than me noticed compilation failures in the clause 21
C++ library test suite in the last day or two? They're manifesting
themselves as compiler timeouts. Example:
Executing on host: /home/austern/obj/gcc/g++ -shared-libgcc
-B/home/austern/obj/gcc/ -nostdinc++
-L/home/austern/obj/i686-pc-linux-gnu/libstdc++-v3/src
-L/home/austern/obj/i686-pc-linux-gnu/libstdc++-v3/src/.libs
-B/home/austern/root/i686-pc-linux-gnu/bin/
-B/home/austern/root/i686-pc-linux-gnu/lib/ -isystem
/home/austern/root/i686-pc-linux-gnu/include -isystem
/home/austern/root/i686-pc-linux-gnu/sys-include -include bits/stdc++.h
-g -O2 -ffunction-sections -fdata-sections -fmessage-length=0
-DLOCALEDIR="/home/austern/obj/i686-pc-linux-gnu/libstdc++-v3/po/share/
locale" -nostdinc++
-I/home/austern/obj/i686-pc-linux-gnu/libstdc++-v3/include/i686-pc-
linux-gnu -I/home/austern/obj/i686-pc-linux-gnu/libstdc++-v3/include
-I/home/austern/gcc34/libstdc++-v3/libsupc++
-I/home/austern/gcc34/libstdc++-v3/libsupc++
-I/home/austern/gcc34/libstdc++-v3/include/backward
-I/home/austern/gcc34/libstdc++-v3/testsuite
/home/austern/gcc34/libstdc++-v3/testsuite/21_strings/basic_string/
inserters_extractors/wchar_t/1.cc -D_GLIBCXX_ASSERT
-L/home/austern/obj/i686-pc-linux-gnu//libstdc++-v3/testsuite -lv3test
-lm -o ./1.exe (timeout = 300)
WARNING: program timed out.
compiler exited with status 1
FAIL: 21_strings/basic_string/inserters_extractors/wchar_t/1.cc (test
for excess errors)
Excess errors:
exit status is 1
WARNING: 21_strings/basic_string/inserters_extractors/wchar_t/1.cc
compilation failed to produce executable
I don't think this can have anything to do with the things I was
testing (library changes in clause 23 stuff); it looks like a compiler
problem. No guesses about what might have caused it, other than that
it must have been recent.
I'm rerunning my tests on a different machine, just to rule out the
possibility of something random like a hardware problem. It would be
nice to know if anyone else has seen this, though.
--Matt