diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml
index fc5a8d4852..bd0b21c9d5 100644
--- a/status/explicit-failures-markup.xml
+++ b/status/explicit-failures-markup.xml
@@ -3685,17 +3685,6 @@ for more information.
                 something else is known to resolve the issue.
             </note>
         </mark-expected-failures>
-        <mark-expected-failures>
-            <test name="test_barrier_lib"/>
-            <toolset name="msvc-8.0"/>
-            <note author="Aleksey Gurtovoy" refid="6"/>
-        </mark-expected-failures>
-
-        <mark-expected-failures>
-            <test name="test_thread"/>
-            <toolset name="msvc-7.1"/>
-            <note author="Aleksey Gurtovoy" refid="6"/>
-        </mark-expected-failures>
 
         <mark-expected-failures reason="?">
             <test name="*_lib"/>
@@ -3714,6 +3703,7 @@ for more information.
             <test name="test_tss_lib"/>
             <toolset name="borland-*"/>
             <toolset name="cw-9.4"/>
+            <toolset name="gcc-mingw*"/>
             <note author="Roland Schwarz" date="2006-12-14">
                 When a thread ends, tss data needs to be cleaned up. This process
                 is mostly automatic. When threads are launched by the Boost.Thread API