From 6e619cdcaec147f6154c5c451e7705ea2eb04e86 Mon Sep 17 00:00:00 2001 From: Automated Commit Date: Thu, 1 Jun 2023 18:25:04 +0000 Subject: [PATCH] Update explicit-failures-markup.xml [skip ci] --- status/explicit-failures-markup.xml | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml index c059cf5b05..ebcb18c7fd 100644 --- a/status/explicit-failures-markup.xml +++ b/status/explicit-failures-markup.xml @@ -995,7 +995,7 @@ - This test fails because `std::uncaught_exception` seems to + This test fails because `std::unchaught_exception` seems to always return zero on this compiler (even if the authors could not find a direct reference to this possible compiler issue online). @@ -2259,6 +2259,19 @@ + + + + + + + + + This compiler is currently not supported. + + + + @@ -2359,8 +2372,8 @@ - The compiler doesn't generate defaulted move ctor/assign thus - perform copy construction/assignment. Even though such case, + The compiler doesn't generate defaulted move ctor/assgin thus + perform copy construction/assginment. Even though such case, the `inline` versions don't force generating move ctor/assign to preserve trivial requirements. Since that is not documented behaviour, it might be changed in future release. @@ -3538,7 +3551,7 @@ for more information. - Workaround: define BOOST_RESULT_OF_USE_TR1 + Wrokaround: define BOOST_RESULT_OF_USE_TR1