More TR1 markup.

gcc-2.95 has some new type-traits failures caused by stronger test cases.


[SVN r32942]

status/explicit-failures-markup.xml

@@ -3317,10 +3317,10 @@ for more information.
         </mark-expected-failures>
         <mark-expected-failures>
             <test name="tricky_function_type_test"/>
+            <test name="is_const_test"/>
+            <test name="is_volatile_test"/>
             <test name="is_convertible_test"/>
-            <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/>
-            <toolset name="gcc-2.95.3-stlport-4.6.2-linux"/>
-            <toolset name="gcc-2.95.3-linux"/>
+            <toolset name="gcc-2*"/>
             <note author="John Maddock" refid="2"/>
         </mark-expected-failures>
         <mark-expected-failures>
@@ -3417,12 +3417,65 @@ for more information.
             <test name="std_run_complex_overloads"/>
             <test name="run_random"/>
             <test name="std_run_random"/>
+            <test name="test_tuple_tricky"/>
+           <test name="tr1_add_const_test"/>
+           <test name="tr1_add_cv_test"/>
+           <test name="tr1_add_pointer_test"/>
+           <test name="tr1_add_reference_test"/>
+           <test name="tr1_add_volatile_test"/>
+           <test name="tr1_aligned_storage_test"/>
+           <test name="tr1_alignment_of_test"/>
+           <test name="tr1_has_nothrow_assign_test"/>
+           <test name="tr1_has_nothrow_constr_test"/>
+           <test name="tr1_has_nothrow_copy_test"/>
+           <test name="tr1_has_trivial_assign_test"/>
+           <test name="tr1_has_trivial_constr_test"/>
+           <test name="tr1_has_trivial_copy_test"/>
+           <test name="tr1_has_trivial_destructor_test"/>
+           <test name="tr1_has_virtual_destructor_test"/>
+           <test name="tr1_is_arithmetic_test"/>
+           <test name="tr1_is_array_test"/>
+           <test name="tr1_is_class_test"/>
+           <test name="tr1_is_compound_test"/>
+           <test name="tr1_is_const_test"/>
+           <test name="tr1_is_convertible_test"/>
+           <test name="tr1_is_empty_test"/>
+           <test name="tr1_is_enum_test"/>
+           <test name="tr1_is_floating_point_test"/>
+           <test name="tr1_is_function_test"/>
+           <test name="tr1_is_fundamental_test"/>
+           <test name="tr1_is_integral_test"/>
+           <test name="tr1_is_member_func_test"/>
+           <test name="tr1_is_member_obj_test"/>
+           <test name="tr1_is_member_pointer_test"/>
+           <test name="tr1_is_object_test"/>
+           <test name="tr1_is_pod_test"/>
+           <test name="tr1_is_pointer_test"/>
+           <test name="tr1_is_polymorphic_test"/>
+           <test name="tr1_is_reference_test"/>
+           <test name="tr1_is_same_test"/>
+           <test name="tr1_is_scalar_test"/>
+           <test name="tr1_is_signed_test"/>
+           <test name="tr1_is_union_test"/>
+           <test name="tr1_is_unsigned_test"/>
+           <test name="tr1_is_void_test"/>
+           <test name="tr1_is_volatile_test"/>
+           <test name="tr1_remove_const_test"/>
+           <test name="tr1_remove_cv_test"/>
+           <test name="tr1_remove_pointer_test"/>
+           <test name="tr1_remove_reference_test"/>
+           <test name="tr1_remove_volatile_test"/>
+           <test name="tr1_tricky_abstract_type_test"/>
+           <test name="tr1_tricky_add_pointer_test"/>
+           <test name="tr1_tricky_partial_spec_test"/>
             <toolset name="borland*"/>
             <note author="John Maddock">
                Support for Borland C++ in the various TR1 libraries is pretty
                poor (due to numerous compiler bugs sadly).  The TR1 concept
                checks are *very* strict, and are expected to fail with this
-               compiler.  More conservative uses are more likely to succeed
+               compiler.  In addition most of the type_traits tests fail
+               whenever debugging support is turned on with an internal
+               compiler error.  More conservative uses are more likely to succeed
                with this compiler however.
             </note>
         </mark-expected-failures>
@@ -3480,6 +3533,12 @@ for more information.
             <test name="test_streambuf"/>
             <test name="test_limits"/>
             <test name="test_locale"/>
+            <test name="test_ios_std_header"/>
+            <test name="test_istream_std_header"/>
+            <test name="test_limits_std_header"/>
+            <test name="test_locale_std_header"/>
+            <test name="test_ostream_std_header"/>
+            <test name="test_streambuf_std_header"/>
             <toolset name="gcc-2*"/>
             <note author="John Maddock">
                These tests fail due to a known compiler bug 
@@ -3488,6 +3547,18 @@ for more information.
             </note>
         </mark-expected-failures>
 
+        <mark-expected-failures>
+           <test name="run_complex_overloads"/>
+           <test name="std_run_complex_overloads"/>
+           <test name="std_test_complex"/>
+           <test name="test_complex"/>
+           <toolset name="qcc-3.3.5-gpp"/>
+            <note author="John Maddock">
+               These tests fail due to a known stdlib bug 
+               that has been reported to the vendor.
+            </note>
+        </mark-expected-failures>
+       
         <mark-expected-failures>
             <test name="tr1_function_traits_test"/>
             <test name="tr1_remove_bounds_test"/>
@@ -3617,10 +3688,10 @@ for more information.
         </mark-expected-failures>
         <mark-expected-failures>
             <test name="tr1_tricky_function_type_test"/>
+            <test name="tr1_is_const_test"/>
+            <test name="tr1_is_volatile_test"/>
             <test name="tr1_is_convertible_test"/>
-            <toolset name="gcc-2.95.3-stlport-4.5.3-linux"/>
-            <toolset name="gcc-2.95.3-stlport-4.6.2-linux"/>
-            <toolset name="gcc-2.95.3-linux"/>
+            <toolset name="gcc-2*"/>
             <note author="John Maddock" refid="2"/>
         </mark-expected-failures>
         <mark-expected-failures>