Does anyone check libstdc++-v3 failures in gcc 3.0?

[H . J . Lu]

Does anyone check those libstdc++v3 failures in gcc 3.0? I saw quite
a few failures on Linux/ia32/glibc 2.2:

+: pass, -b: build failure, -r: run failure, x: disabled
------------------------------------------------------------------------
static  shared  test
------------------------------------------------------------------------
-r      +       21_strings/ctor_copy_dtor.cc
-r      +       21_strings/element_access.cc
-r      +       21_strings/insert.cc
-r      +       21_strings/substr.cc
-b      -b      23_containers/map_operators.cc
-b      -b      23_containers/set_operators.cc
-b      -b      26_numerics/c99_macros.cc
-b      -b      27_io/filebuf.cc
-r      -r      27_io/ios_base_members_static.cc
-r      -r      27_io/istream_extractor_char.cc
-b      -b      27_io/istream_seeks.cc
+       +       27_io/istream_sentry.cc
diff: ./istream_unformatted-2.txt: No such file or directory
+       diff: ./istream_unformatted-2.txt: No such file or directory
+       27_io/istream_unformatted.cc

I don't think it is too hard to modify contrib/test_summary and
libstdc++-v3/mkcheck.in to send in test summary for libstdc++-v3.
It will help keeping track the status of libstdc++-v3. I can provide
a patch if everyone agrees it is a good idea and noone has any time.
I hope gcc 3.0 will ship a working libstdc++ which at least passes its
own testsuite. That is what gcc had been doing before gcc 3.0.

Thanks.


H.J.