This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Regressions running the libstdc++ test suite (gcc 3.0)
- To: libstdc++ at gcc dot gnu dot org
- Subject: Regressions running the libstdc++ test suite (gcc 3.0)
- From: Peter Schmid <schmid at snake dot iap dot physik dot tu-darmstadt dot de>
- Date: Fri, 8 Jun 2001 14:57:36 +0200 (CEST)
- cc: gcc at gcc dot gnu dot org
There are two new regressions running the libstdc++ test suite on the
i686-pc-linux-gnu target.
Both executables consume all of the virtual memory, until they are killed by
the linux operating system by a SIGKILL signal. It makes no difference
if the executables run within the test suite; or if I install the
compiler and then compile and link the executables directly.
These bug were not present when I last built the compiler; the
executables generated by gcc 20010604 ran without a problem.
Hope this helps,
Peter Schmid
System setup: SuSE 7.1, glibc 2.2, binutils 2.11.90.0.4, linux 2.4.4.
Output of gcc -v:
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.0/specs
Configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads=posix --enable-long-long --enable-languages=c,c++,f77,objc
Thread model: posix
gcc version 3.0 20010608 (prerelease)
Excerpt of libstdc++.log:
Running /mnt/egcs/gcc/libstdc++-v3/testsuite/libstdc++-v3.dg/dg.exp ...
FAIL: 21_strings/ctor_copy_dtor.cc execution test
FAIL: 21_strings/insert.cc execution test
=== libstdc++-v3 Summary ===
# of expected passes 241
# of unexpected failures 2
# of expected failures 8