Просмотр исходного кода

Removed "mark-expected-failures" from value_init_test, for both Borland and GCC, as value_init.hpp changeset [41942] provides a workaround for them.

[SVN r42196]
Niels Dekker 18 лет назад
Родитель
Сommit
d6cc24af79
1 измененных файлов с 0 добавлено и 37 удалено
  1. 0 37
      status/explicit-failures-markup.xml

+ 0 - 37
status/explicit-failures-markup.xml

@@ -5484,43 +5484,6 @@ choosing instead to bind them to the private (and unimplemented) copy constructo
                 versions of the compiler (VC 7.1 and greater).
             </note>
         </mark-expected-failures>
-        <mark-expected-failures>
-            <test name="value_init_test"/>
-            <toolset name="borland-5.6*"/>
-            <toolset name="borland-5.8*"/>
-            <toolset name="borland-5.9*"/>
-            <note author="Niels Dekker">
-                This test typically fails on Borland C++, because of an issue described by
-                <a href="http://svn.boost.org/trac/boost/ticket/1459">
-                ticket #1459, "value_initialized leaves data uninitialized,
-                when using Borland"</a>. The issue is caused by a 
-                compiler bug, reported at the website of Codegear/Borland:
-                <a href="http://qc.codegear.com/wc/qcmain.aspx?d=51854">
-                Report #51854, "Value-initialization: POD struct
-                should be zero-initialized"</a>.
-            </note>
-        </mark-expected-failures>
-        <mark-expected-failures>
-            <test name="value_init_test"/>
-            <toolset name="gcc-3.3*"/>
-            <toolset name="gcc-3.4*"/>
-            <toolset name="gcc-4.0*"/>
-            <toolset name="gcc-4.1*"/>
-            <toolset name="gcc-4.2*"/>
-            <toolset name="gcc-mingw-3.4*"/>
-            <note author="Niels Dekker">
-                This test typically fails on GCC, because of an issue described by
-                <a href="http://svn.boost.org/trac/boost/ticket/1491">
-                ticket #1491, "value_initialized leaves data uninitialized,
-                when using GCC"</a>. The issue is caused by some GCC compiler bugs:  
-                <a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30111">
-                Value-initialization of POD base class doesn't initialize members</a>,
-                reported by Jonathan Wakely, and
-                <a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33916">
-                Default constructor fails to initialize array members</a>,
-                reported by Michael Elizabeth Chastain. 
-            </note>
-        </mark-expected-failures>
         <mark-expected-failures>
             <test name="operators_test"/>
             <toolset name="gcc-3.4.5_linux_x86_64"/>

粤ICP备19079148号