organicmaps/boost
13
Fork 0
mirror of https://github.com/boostorg/boost.git synced 2025-04-05 21:45:00 +00:00
Code Issues 1 Projects Releases Wiki Activity Actions

Update explicit-failures-markup.xml

Browse source 
[skip ci]
This commit is contained in:
Automated Commit 2018-01-20 18:25:43 +00:00
parent 64fda8b5f7
commit 465b9b2329
1 changed files with 5 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
status/explicit-failures-markup.xml
View file

@ -912,7 +912,7 @@
<note author="Lorenzo Caminiti">
Even tests that do not use C++11 lambda functions fail on this
compiler because it incorrectly attempts an extra copy when
objects are constructed via `boost::check c = ...`.
objects are constructed using `boost::check c = ...`.
This is fixed in MinGW GCC 4.3.
</note>
</mark-unusable>
@ -920,11 +920,10 @@
<toolset name="msvc-7.1"/>
<note author="Lorenzo Caminiti">
Even tests that do not use C++11 lambda functions fail on this
compiler because of a number of different issues
(Boost.Exception, which used by this library, also is not
supported on this compiler, incorrect implementation of some
aspects of friendship, incorrect dispatching of some `volatile`
calls, etc.).
compiler because of a number of issues (Boost.Exception is not
supported on this compiler but it is used by this library
implementation, some aspects of `friend` and `volatile` are not
properly implemented on this compiler, etc.).
These specific issues are fixed in MSVC 9.0 (but only MSVC 11.0
has adequate lambda function support that makes this library
actually usable).
@ -1151,17 +1150,6 @@
lambda function support).
</note>
</mark-expected-failures>
<!-- following due to other boost libs, could be fixed in master? -->
<mark-expected-failures>
<test name="old-auto"/>
<test name="old-copyable_traits"/>
<toolset name="gcc-4.6c+"/>
<note author="Lorenzo Caminiti">
This test fails because of this compiler/platform cause an
error in Boost.TypeTraits (this could be fixed in the master
branch... not sure).
</note>
</mark-expected-failures>
</library>
<!-- coroutine -->