<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 7, 2017, at 11:55 AM, Taylor Swift <<a href="mailto:kelvin13ma@gmail.com" class="">kelvin13ma@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Sep 7, 2017 at 12:31 PM, Andrew Trick <span dir="ltr" class=""><<a href="mailto:atrick@apple.com" target="_blank" class="">atrick@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><blockquote type="cite" class=""><span class=""><div class="">On Sep 7, 2017, at 8:06 AM, Taylor Swift <<a href="mailto:kelvin13ma@gmail.com" target="_blank" class="">kelvin13ma@gmail.com</a>> wrote:</div><br class="m_-5510455431031613542Apple-interchange-newline"></span><div class=""><span class=""><div dir="ltr" class="">I don’t see any source for this claim in the <a href="https://developer.apple.com/documentation/swift/unsafemutablepointer/2295090-deallocate" target="_blank" class="">documentation</a>, or the <a href="https://github.com/apple/swift/blob/master/stdlib/public/core/UnsafePointer.swift.gyb#L432" target="_blank" class="">source code</a>. As far as I can tell the expected behavior is that partial deallocation “should” work.<br class=""></div></span><div class="gmail_extra"><br class=""><div class="gmail_quote"><span class="">On Thu, Sep 7, 2017 at 8:59 AM, Joe Groff <span dir="ltr" class=""><<a href="mailto:jgroff@apple.com" target="_blank" class="">jgroff@apple.com</a>></span> wrote:</span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_-5510455431031613542HOEnZb"><div class="m_-5510455431031613542h5">
<br class="">
</div></div>The segfaulting example is an incorrect usage. The only valid parameters to deallocate(capacity:) are the base address of an allocation, and the original capacity passed into allocate(); it has never been intended to support partial deallocation of allocated blocks. It seems to me like this proposal is based on a misunderstanding of how the API works. The documentation and/or name should be clarified.<br class="">
<span class="m_-5510455431031613542HOEnZb"><font color="#888888" class=""><br class="">
-Joe<br class="">
</font></span><div class="m_-5510455431031613542HOEnZb"><div class="m_-5510455431031613542h5"><br class="">
> “fixing” this bug will cause programs that once operated on previously valid assumptions of “free()” semantics to behave differently, without any warnings ever being generated. Conversely incorrect code will suddenly become “correct” though this is less of a problem.<br class="">
><br class="">
>> A sized implementation may fail more obviously when you violate the contract in the future. Not having sized deallocation is a known deficiency of the C model we've been fairly diligent about avoiding in Swift's allocation interfaces, and it would be extremely unfortunate for us to backpedal from it.<br class="">
>><br class="">
>> -Joe<br class=""></div></div></blockquote></span></div></div></div></blockquote><br class=""></div><div class=""><div class="">This discussion needs to be grounded by reiterating role of the API. UnsafePointer specifies the memory model without extraneous functionality or convenience.</div><div class=""><br class=""></div><div class="">The UnsafePointer.deallocate() API *is not*:</div><div class=""><br class=""></div><div class="">- a common, expected, or encouraged way to deallocate</div><div class=""><br class=""></div><div class="">- the simplest, safest, or most convenient way to deallocate</div><div class=""><br class=""></div><div class="">- necessarilly the most optimal path for deallocation</div><div class=""><br class=""></div><div class="">There is only one decision that needs to be made here. Does the Swift runtime track allocation size for manually allocated blocks? I think the answer should be "yes", or at least haven't heard a strong argument against it. UnsafePointer.deallocate() needs to direcly reflect that model by making `allocatedCapacity` an *optional* argument.</div><div class=""><br class=""></div><div class="">Discussion about whether this API is unsafe, misleading, suboptimal or incorrectly implemented are secondary. Those are all deficiencies in the current documentation, current implementation, and availability of higher-level APIs.</div><div class=""><br class=""></div><div class="">Note that yesterday I argued that an optional argument wasn't worth the potential for confusion. That's true from a practical perspective, but I had lost sight of need to clearly specify the memory model. We want the Swift runtime to both have the functionality for tracking block size and also allow user code to track it more efficiently. Both those intentions need to be reflected in this API.</div><div class=""><br class=""></div></div><div class="">-Andy</div></div></blockquote></div></div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">idk how the swift heap is planned to be implemented, but why is passing the capacity to <span style="font-family:monospace,monospace" class="">deallocate</span> considered the fast path anyway? i thought the block size was stored in a header right before the block pointer<br class=""></div></div>
</div></blockquote><br class=""></div><div>It doesn't have to be. When all allocation and deallocation calls carry matching capacity values, then that overhead can be eliminated when allocating out of a heterogeneous heap. Optimized allocators also generally have per-thread pools for common allocation sizes, and if you have the capacity value on hand, it can be quickly matched to the right pool size, and constant allocation sizes can potentially be recognized by the compiler and turned into allocator calls that directly allocate out of a specific pool.</div><div><br class=""></div><div>-Joe</div><br class=""></body></html>