Displaying 2 results from an estimated 2 matches for "deallocation_".
Did you mean:
deallocation
2008 May 05
0
[LLVMdev] optimization assumes malloc return is non-null
...ended and before the storage which the
object
occupied is reused or released, any pointer that refers to the
storage
location where the object will be or was located may be used but
only
in limited ways. Such a pointer refers to allocated
storage
(_basic.stc.dynamic.deallocation_), and using the pointer as if
the
pointer were of type void*, is well-defined. Such a pointer may
be
dereferenced but the resulting lvalue may only be used in
limited
ways, as described below.
[ see the rest of the standard for all the gory details. ]
>>> A lot...
2008 May 01
3
[LLVMdev] optimization assumes malloc return is non-null
(Hi Mike!)
On May 1, 2008, at 6:11 PM, Mike Stump wrote:
> On Apr 30, 2008, at 9:26 PM, Chris Lattner wrote:
>> Personally to me, I have a bigger axe to grind with C++ operator new.
>> AFAIK, the standard doesn't give leeway to do a number of interesting
>> optimizations for new/delete because the user is explicitly allowed
>> to
>> override them and the std