This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author josh.r
Recipients josh.r, pitrou, vstinner
Date 2014-05-02.20:59:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399064362.41.0.320751040863.issue21419@psf.upfronthosting.co.za>
In-reply-to
Content
Looks like you forgot to actually use the use_calloc parameter you put in the long_alloc prototype. It accepts it, but it's never used or passed to another function. So right now, the only difference in behavior is that there is an extra layer of function calls involved in _PyLong_New.

On that note, might it make sense to change all other calls to _PyLong_New within longobject.c to use long_alloc(size, 0) to at least make long object's themselves avoid the overhead of the extra function call? Maybe I'm overestimating how much of a difference an extra C level function call will make, but it seems like PyLongs make new PyLongs an awful lot.
History
Date User Action Args
2014-05-02 20:59:22josh.rsetrecipients: + josh.r, pitrou, vstinner
2014-05-02 20:59:22josh.rsetmessageid: <1399064362.41.0.320751040863.issue21419@psf.upfronthosting.co.za>
2014-05-02 20:59:22josh.rlinkissue21419 messages
2014-05-02 20:59:21josh.rcreate
Morty Proxy This is a proxified and sanitized view of the page, visit original site.