diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml
index 6b33ec6419..4bcbffdad3 100644
--- a/status/explicit-failures-markup.xml
+++ b/status/explicit-failures-markup.xml
@@ -346,6 +346,13 @@
+
+
+
+
+ This failure is only present in release mode and is caused by /OPT:ICF.
+
+
@@ -357,6 +364,14 @@
+
+
+
+
+
+
+
+
@@ -1094,6 +1109,13 @@
More recent version of the library should work OK.
+
+
+
+
+ fstream for this compiler has serious problems and is not supported
+
+
@@ -1523,6 +1545,16 @@
+
+
+
+
+ I'm not sure whether CodeWarrior is correct to report that the member
+ in question is inaccessible; however, when the member is made public
+ an internal error occur that I have not been able to fix, so for
+ now the question is moot.
+
+
@@ -2342,6 +2374,8 @@ for more information.
+
+
@@ -3411,20 +3445,20 @@ for more information.
use and building of dll's mainly.
-
-
-
-
- GCC on tru64 appears not to cope with C++ exceptions
- thrown from within threads.
-
-
-
+
+
+
+
+ GCC on tru64 appears not to cope with C++ exceptions
+ thrown from within threads.
+
+
+
-
+
@@ -3452,13 +3486,6 @@ for more information.
-
-
-
-
-
-
-
@@ -3467,8 +3494,25 @@ for more information.
There appears to be a linker bug that prevents these
projects from building, see http://qc.borland.com/wc/qcmain.aspx?d=32020.
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ There appears to be a linker bug that prevents these
+ projects from building, see http://qc.borland.com/wc/qcmain.aspx?d=32020.
+
+
+
@@ -3698,17 +3742,23 @@ for more information.
-
+
-
+
+
+
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
@@ -4116,9 +4166,10 @@ for more information.
+
These tests fail due to a known compiler bug
- that is fixed in more recent releases. Users are
+ that is fixed in more recent GNU compiler releases. Users are
very unlikely to encounter this as a real problem
in practice.
@@ -4258,6 +4309,7 @@ for more information.
+