search for: n3433

See also this proposal for the next C++ committee meeting, which aims to clarify this case and others like it: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3433.html On Tue, Oct 2, 2012 at 9:49 AM, Reed Kotler <rkotler at mips.com> wrote: > I've sent this issue to some friends on the C++ committee. > > The first response I received indicates that the person thinks the > optimizer is within it's rights to optimize away the call t...

I've sent this issue to some friends on the C++ committee. The first response I received indicates that the person thinks the optimizer is within it's rights to optimize away the call to malloc. Here are some points, extracted from the response: "There is no observable behavior (a technical term in the standard) that violates requirements of the standard. In particular, malloc in