id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
4080	Various compilers need BOOST_NO_COMPLETE_VALUE_INITIALIZATION	niels_dekker	niels_dekker	"John Maddock has just added my boost_no_complete_value_initialization tests to the trunk: https://svn.boost.org/svn/boost/trunk/libs/config/test/boost_no_com_value_init.ipp [61153], which is likely to cause some regression failures. This ticket is there to remind me to keep an eye at the regression page: http://www.boost.org/development/tests/trunk/developer/config_.html And to define the new defect macro, BOOST_NO_COMPLETE_VALUE_INITIALIZATION, for those compilers that appear to get those regression failures.

Moreover, this ticket allows archiving the regression failure output for those compilers, before those failures are suppressed by means of the defect macro.

Related ticket: #3869, ""Unconditional call to 
memset in value_initialized()"", reported by Aleksey Gurtovoy.

Related mailing list item: [boost] [config] New defect macro:BOOST_NO_COMPLETE_VALUE_INITIALIZATION"	Bugs	closed	Boost 1.43.0	config	Boost 1.42.0	Problem	fixed