7 Jan
2010
7 Jan
'10
9:47 p.m.
"Peter Foelsche" <peter_foelsche@agilent.com> wrote in message news:h7rie8$i9u$1@ger.gmane.org...
"Aleksey Gurtovoy" <agurtovoy@meta-comm.com> wrote in message news:op.uzp57jgyccf1k7@wonderland.office.meta...
Could you verify whether the gcc will optimize away the rest of the value_initialized magic if the memset is out?
Ok -- I removed memset from value_initialized and I restored for_each.hpp to is original state. Now gcc 4.4.1 with optimization also does not create any (assembler) code for the initialization of this anyway not used parameter.
in boost_1_41_0 there is still an unconditional call to memset in value_initialized() Peter