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

Marked value_init_test failures on Borland C++ as "expected failures", as discussed with Fernando Cacciola.

Browse source 
[SVN r41402]
This commit is contained in:
Niels Dekker 2007-11-26 17:36:52 +00:00
parent 7bad39f8de
commit 09b93cdf7f
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -5408,6 +5408,22 @@ for more information.
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="operators_test"/>
<toolset name="gcc-3.4.5_linux_x86_64"/>