diff --git a/status/explicit-failures-markup.xml b/status/explicit-failures-markup.xml index 90934a9633..2927e6a671 100644 --- a/status/explicit-failures-markup.xml +++ b/status/explicit-failures-markup.xml @@ -894,15 +894,11 @@ - + - Tests fail to link on this compiler when libc++ is used (see + Tests fail to link on this compiler because of a bug in its STL + implementation (undefined references to `operator delete`, see https://tracker.crystax.net/issues/1403). - This linker error does not occur with libstdc++ but - unfortunately the toolset name for this compiler does not - differentiate between libc++ and libstdc++ runs so also - libstdc++ tests had to be marked as expected failures (even if - they actually pass). @@ -931,25 +927,26 @@ - - + + + + + - This test fails on this compiler because of a bug in libc++ - (see http://grokbase.com/t/gg/android-ndk/1656csqqtp/assertion-ttypeencoding-dw-eh-pe-absptr-unexpected-ttypeencoding-failed). - This is fixed in libstdc++. + This test fails on this compiler because of a bug with + exceptions (see http://grokbase.com/t/gg/android-ndk/1656csqqtp/assertion-ttypeencoding-dw-eh-pe-absptr-unexpected-ttypeencoding-failed). - - This test fails on this compiler because of a bug in libstdc++ - (undefined references to `std::ios_base::failure::failure`). - This is fixed in libc++. + This test fails on this compiler because of a bug in its STL + implementation (undefined references to + `std::ios_base::failure::failure`). @@ -976,6 +973,7 @@ +