Added markup for expected Borland failures with TR1.

[SVN r32472]

status/explicit-failures-markup.xml

@@ -3233,6 +3233,43 @@ for more information.
             </note>
         </mark-expected-failures>
 
+        <mark-expected-failures>
+            <test name="test_array"/>
+            <test name="std_test_array"/>
+            <test name="test_complex"/>
+            <test name="std_test_complex"/>
+            <test name="test_function"/>
+            <test name="std_test_function"/>
+            <test name="test_mem_fn"/>
+            <test name="std_test_mem_fn"/>
+            <test name="test_random"/>
+            <test name="std_test_random"/>
+            <test name="test_regex"/>
+            <test name="std_test_regex"/>
+            <test name="test_result_of"/>
+            <test name="std_test_result_of"/>
+            <test name="test_shared_ptr"/>
+            <test name="std_test_shared_ptr"/>
+            <test name="test_tr1_include"/>
+            <test name="std_test_tr1_include"/>
+            <test name="test_tuple"/>
+            <test name="std_test_tuple"/>
+            <test name="test_type_traits"/>
+            <test name="std_test_type_traits"/>
+            <test name="run_complex_overloads"/>
+            <test name="std_run_complex_overloads"/>
+            <test name="run_random"/>
+            <test name="std_run_random"/>
+            <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
+               with this compiler however.
+            </note>
+        </mark-expected-failures>
+
         <mark-expected-failures>
             <test name="std_test_bind"/>
             <test name="test_bind"/>