From 733b5d5ae2c5d625211e2985ac25728ac3f54883 Mon Sep 17 00:00:00 2001 From: DongHun Kwak Date: Mon, 21 Mar 2016 15:45:20 +0900 Subject: Imported Upstream version 1.58.0 Change-Id: If0072143aa26874812e0db6872e1efb10a3e5e94 Signed-off-by: DongHun Kwak --- status/explicit-failures-markup.xml | 380 ++++++++++++++++++++++++++++++------ 1 file changed, 316 insertions(+), 64 deletions(-) (limited to 'status/explicit-failures-markup.xml') diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml index 98607832e4..3fa5892e1c 100644 --- a/status/explicit-failures-markup.xml +++ b/status/explicit-failures-markup.xml @@ -85,6 +85,21 @@ + + + + + + + + + + + These failures are caused by a lack of support/configuration for Boost.Tr1 + + + + @@ -488,7 +503,7 @@ - + The compiler does not support features that are essential for the library. @@ -631,8 +646,23 @@ - - + + + + + + + + + + The relevant SFINAE support is broken in MSVC up to version 11. + + + + + + + @@ -649,15 +679,6 @@ - - - - - - This compiler is unable to compile Boost.Container library - - - @@ -678,19 +699,22 @@ + + + - Conversion double-string-double may give a different value (or even throw) on many compilers + Conversion double-string-double may give a different + value (or even throw) on many compilers - - + @@ -698,28 +722,41 @@ + - Some compilers and STL realizations convert double and long double types with bigger precision loss than minimal (or even round to infinity). Such failures are not a lexical_cast, but a compiler fault. + Some compilers and STL realizations convert double and long + double types with bigger precision loss than minimal (or + even round to infinity). Such failures are not a + lexical_cast, but a compiler fault. + - - - + + + + + + + + + + + - + @@ -1435,13 +1472,18 @@ + + + + + - + @@ -1993,12 +2035,12 @@ - - + - - + + + These compilers do not support features that are essential for the library. @@ -2011,6 +2053,12 @@ Intel 11.1 and 12.0 on Darwin raises a SIGSEGV in almost all unit tests. + + + + Intel 13.1.3 does not support BOOST_TEST + + @@ -2025,6 +2073,36 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2075,6 +2153,7 @@ + Compiler error expected for msvc: A minimal example of a class template 'value' that results in syntax error in a subsequent meta function. @@ -2512,13 +2591,31 @@ + + This test does not allow C++11 auto-declaration support - (beccause it uses the `auto` keyword as storage classifier). + (because it uses the `auto` keyword as storage classifier). + + + + + + The compiler fails to compile Boost.Move and Boost.PropertyTree, which are used by this library. + + + + + + Boost.Filesystem used by Boost.Log does not support Windows Mobile. + + + + @@ -2839,9 +2936,129 @@ for more information. + + + + + + + + +

+ These compilers are too antiquated for this library. +

+ + + + + + + + + +

+ These compilers don't quite have the necessary support for this library, it's possible + that they could be made to work if someone cares enough. +

+ + - + + + + + + + + + + + + + + + + + + + + + + This failure is caused by a test-runner timeout: unfortunately the Intel + compiler is exceptionally slow at building some of these tests. + + + + + + + + + This failure is caused by a test-runner timeout. + + + + + + + + + +

This is a compiler bug: it sometimes creates an illegal temporary object. + The following code illustrates the bug:

+ 
+		#include <cassert>
+		const int global_i = 0;
+		
+		struct TestingReferenceBinding
+		{
+		  void operator=(const int& ii)
+		  {
+		    assert(&ii == &global_i);
+		  }
+		};
+		
+		int main()
+		{
+		  TestingReferenceBinding ttt;
+		  ttt = global_i;
+		}
+
+ + + + + + + + + + + + + +

This is a compiler bug: it sometimes creates an illegal temporary object. + The following code illustrates the bug:

+ 
+		#include <cassert>
+		const int global_i = 0;
+		
+		struct TestingReferenceBinding
+		{
+		  TestingReferenceBinding(const int& ii)
+		  {
+		    assert(&ii == &global_i);
+  		  }
+		};
+		
+		int main()
+		{
+		  TestingReferenceBinding ttt = global_i;
+		}
+
+ + @@ -2851,11 +3068,19 @@ for more information. + + + + + + + +

This failure is caused by a compiler bug, and as far as we can tell, can't be worked around in the library, although we think @@ -4836,7 +5061,7 @@ for more information. - + The compiler does not support features that are essential for this test . @@ -5325,40 +5550,6 @@ for more information. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -This test uses Boost.Test and Boost.Test doesn't works on this compiler. - - @@ -5465,6 +5656,7 @@ The implementation of native_handle() is not possible on this platform. + @@ -5476,11 +5668,26 @@ The implementation of native_handle() is not possible on this platform. - - + + + + + + + + + This platform doesn't supports Boost.Chrono. + + + + +This platform doesn't supports Boost.Container. + + + @@ -5534,6 +5741,48 @@ This platform doesn't supports Boost.Chrono. + + + + + + + + + + + + + + + + + + + + + + + + Classes with exactly the same names defined in different modules in anonymous namespaces collapse + for this compiler even with RTTI on. This is a known compiler limitation that already fixed + in newer versions or will be fixed soon. + + + + + + + + + + Classes with exactly the same names defined in different modules in anonymous namespaces collapse + for this compiler with RTTI off. This is a known limitation of RTTI-off mode. Such behavior is + reflected in docs. + + + + @@ -5625,6 +5874,9 @@ This platform doesn't supports Boost.Chrono. + + + See bug 99776 'enum UIntEnum { value = UINT_MAX } is promoted to int' http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=22b0a6b7-120f-4ca0-9136-fa1b25b26efe -- cgit v1.2.3