From a477d70f32736c1ff010e5cadd6489109543d664 Mon Sep 17 00:00:00 2001
From: Daniel James <daniel@calamity.org.uk>
Date: Wed, 10 Jan 2018 11:46:13 +0000
Subject: [PATCH] Add explicit failure for noexcept_tests on gcc + fix
 description for Visual C++ 7.1

---
 meta/explicit-failures-markup.xml | 19 +++++++++++++++----
 1 file changed, 15 insertions(+), 4 deletions(-)

diff --git a/meta/explicit-failures-markup.xml b/meta/explicit-failures-markup.xml
index 7ab7ce7e..4a49114a 100644
--- a/meta/explicit-failures-markup.xml
+++ b/meta/explicit-failures-markup.xml
@@ -17,11 +17,22 @@
         <test name="compile_map_unordered_allocator"/>
         <toolset name="msvc-7.1"/>
         <note author="Daniel James">
-            This tests whether inserting elements creates as few copies as I think
-            is possible. If this fails it just means that the container might be
-            a little inefficient.
+            This test fail because it's using unordered's internal
+            allocator traits, which doesn't work on Visual C++ 7.1.
+            It normally uses the one from Boost.Container by default.
         </note>
       </mark-expected-failures>
-    </library>
+
+      <mark-expected-failures>
+        <test name="noexcept_tests"/>
+        <toolset name="gcc-4.3c+"/>
+        <note author="Daniel James">
+            boost::is_nothrow_move_constructible and
+            boost::is_nothrow_move_assignable don't seem to work on this
+            compiler. I'd hope that anyone wanting noexcept support would
+            use a more recent compiler anyway.
+        </note>
+      </mark-expected-failures>
+      </library>
 </explicit-failures-markup>