Boost C++ Libraries: Ticket #4080: Various compilers need BOOST_NO_COMPLETE_VALUE_INITIALIZATION

niels_dekker — Fri, 23 Apr 2010 22:01:57 GMT

(In [61516]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to IBM XL C++ <= V10.1.0 (trunk), see #4080.

niels_dekker — Fri, 23 Apr 2010 22:12:43 GMT

I just added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to https://svn.boost.org/svn/boost/trunk/boost/config/compiler/vacpp.hpp because IBM's XL C/C++ for AIX V10.1.0.0 did not value-initialize enum_holder_and_int(), virtual_destructor_holder(), and non_pod_class() from https://svn.boost.org/svn/boost/trunk/libs/config/test/boost_no_com_value_init.ipp revision [61436], according to the Config/trunk regression data provided by IBM_Canada_Ltd.

niels_dekker — Wed, 28 Apr 2010 08:50:25 GMT

(In [61642]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to GCC < 4.4 (trunk), see #4080.

niels_dekker — Wed, 28 Apr 2010 17:54:06 GMT

(In [61652]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to Borland (trunk), see #4080

niels_dekker — Thu, 29 Apr 2010 21:49:46 GMT

Adding BOOST_NO_COMPLETE_VALUE_INITIALIZATION to http://svn.boost.org/svn/boost/trunk/boost/config/compiler/borland.hpp ([61652]) fixed the related regression failures of siliconman/borland-5.9.3 (config_test + config_test_threaded), but it did not fix any regression failure of siliconman/borland-6.1.3, siliconman/borland-6.2.1, codegear/borland-cb2009, or borland-cb2010. So the defect macro still needs to be added to http://svn.boost.org/svn/boost/trunk/boost/config/compiler/codegear.hpp

niels_dekker — Thu, 29 Apr 2010 22:32:46 GMT

(In [61691]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to CodeGear (trunk), see #4080.

niels_dekker — Sat, 01 May 2010 22:28:26 GMT

(In [61725]) Redid adding BOOST_NO_COMPLETE_VALUE_INITIALIZATION to IBM XL C++ <= V10.1.0 (trunk), as [61516]. The addition of heap objects to boost_no_complete_value_initialization::test() [61552] did not cause any extra failures. See #4080.

niels_dekker — Mon, 03 May 2010 17:43:57 GMT

(In [61744]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to Sun <= 5.10 (trunk), see #4080

niels_dekker — Wed, 05 May 2010 20:46:42 GMT

(In [61799]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to Microsoft Visual C++ (trunk), see #4080.

niels_dekker — Fri, 07 May 2010 20:05:48 GMT

(In [61848]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to IBM XL C++ <= V11.0.1 (trunk), see #4080.

niels_dekker — Wed, 12 May 2010 18:23:35 GMT

(In [61933]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to IBM XL C++ <= V11.1 (trunk), see #4080.

niels_dekker — Fri, 14 May 2010 21:51:15 GMT

(In [61971]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to clang (trunk), see #4080.

niels_dekker — Wed, 19 May 2010 09:54:11 GMT

(In [62094]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to VC++ 10.0 (trunk), see #4080.

niels_dekker — Sat, 22 May 2010 22:27:29 GMT

(In [62159]) Added BOOST_NO_COMPLETE_VALUE_INITIALIZATION to Intel C++ <= 11.1 (trunk), see #4080.

viboes — Wed, 16 Jan 2013 23:10:39 GMT

Couldn't this ticket be closed?

status changed; resolution set

niels_dekker — Sun, 20 Jan 2013 14:37:52 GMT

status new → closed
resolution → fixed

Thanks, Vicente. I agree with you; I'll close the ticket. Of course future compiler versions might need this defect-macro as well...

Note that for Microsoft Visual C++, with revision [78468] the defect-macro is defined unconditionally (independent of its compiler version). Unfortunately the current Boost Config test cannot detect when this defect-macro is defined unnecessarily. (If a future version of Visual C++ would ever completely implement value-initialization, BOOST_NO_COMPLETE_VALUE_INITIALIZATION would still remain there for this compiler.) But that issue is beyond the scope of this ticket.