I understand, but allowing users to override new means that the actual
implementation may not honor the aliasing guarantees of attribute
malloc.
-Chris
http://nondot.org/sabre
http://llvm.org
On Sep 7, 2007, at 10:12 PM, Joe Buck <[EMAIL PROTECTED]> wrote:
On Sep 7, 2007, at 1:53 PM, Martin Jambor wrote:
[ giving operator new the malloc property ]
On Fri, Sep 07, 2007 at 06:30:33PM -0700, Chris Lattner wrote:
It is unclear whether this is safe. Nothing in the standard AFAIK
requires the operator new be implemented in terms of malloc, and
users are allowed to override it.
The malloc property doesn't mean that operator new is defined in terms
of malloc. It refers to the aliasing properties of the returned
values; specifically, the compiler can assume that two separate calls
return values that don't alias each other.
