3.3 branch libstdc++ testresults

[Benjamin Kosnik]

>The 19_*, 21_* and 23_* failures are not found for gcc-3.2.1, so these
>seem to be regressions. Is there a way to find out, which testcases
>exactly fail?

Run them on a simulator?

>FAIL: 19_diagnostics/stdexceptions.cc execution test
>FAIL: 20_util/allocator_members.cc execution test
>FAIL: 21_strings/append.cc execution test
>FAIL: 21_strings/ctor_copy_dtor.cc execution test
>FAIL: 21_strings/element_access.cc execution test
>FAIL: 21_strings/insert.cc execution test
>FAIL: 21_strings/substr.cc execution test
>FAIL: 22_locale/ctor_copy_dtor.cc execution test
>FAIL: 23_containers/bitset_ctor.cc execution test
>FAIL: 23_containers/bitset_members.cc execution test
>FAIL: 23_containers/deque_ctor.cc execution test
>FAIL: 23_containers/list_modifiers.cc execution test
>FAIL: 23_containers/vector_capacity.cc execution test
>FAIL: 23_containers/vector_ctor.cc execution test
>FAIL: 23_containers/vector_element_access.cc execution test
>FAIL: 23_containers/vector_resize.cc execution test
>FAIL: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
>FAIL: 27_io/ios_base_storage.cc execution test
>FAIL: 27_io/ios_init.cc execution test
>FAIL: 27_io/ios_members.cc execution test
>FAIL: thread/pthread4.cc execution test

Most of these new failures look to be related to exception handling in
general. You might want to try the gcc-3.2.2 release to see if that
works.

-benjamin