[LLVMdev] Memory Allocation Optimized away with new by not with ::operator new

Fran├žois Fayard fayard.francois at icloud.com
Mon May 4 08:51:29 PDT 2015


> On 04 May 2015, at 17:47, David Blaikie <dblaikie at gmail.com> wrote:
> 
> I believe the notion was to provide a syntax for /actually/ calling those functions that the compiler couldn't optimize away, in case you wanted them for their side effects, etc.

That makes sense.

By the way, does anybody know an example where LLVM can fuse 2 memory allocation into one? In N3664, it is explicitly said that the compiler is allowed to do that.



More information about the llvm-dev mailing list