> > This should be a C++ front-end bug. The specific operator new > from <new> used in this placement-new should be folded, > even if -fno-inline. Jason, is this something easily fixable? > > After overload resolution, we know exactly which operator new > we are picking, and we know it is the one coming from the > implementation with its definition. So we should be good to go.
Great! I think this is quite important starting point to get some heap optimizations done in middle-end :) Honza
