Displaying 2 results from an estimated 2 matches for "allocated34".
Did you mean:
allocated
2008 May 05
0
[LLVMdev] optimization assumes malloc return is non-null
...ould work
> if instead of
> "double", a type with a destructor was used. Worth investigating?
Yes, there are various bits in the lifetime rules that also constrain:
5 Before the lifetime of an object has started but after the storage
which the object will occupy has been allocated34) or, after the
life-
time of an object has 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...
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