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 nascheme
Recipients benjamin.peterson, fweimer, gregory.p.smith, methane, nascheme, pitrou, skrah, tgrigg, twouters, vstinner
Date 2019-05-22.00:02:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> sys.getsizeof(3.14) is 24.  And it becomes 32 byte in 16byte aligned pymalloc. (+33%)

I've been doing some reading and trying to understand this issue.  My understanding is that malloc() needs to return pointers that are 16-byte aligned on AMD64 but, in general, pointers don't have the be aligned that way.  If you have a structure that contains a "long double" then that member also has to be 16-bit aligned.

It seems to me that we don't need to have the PyObject structure containing a Python float to be 16-byte aligned.  If so, could we introduce a new obmalloc API that returns memory with 8-byte alignment, for use by objects that know they don't require 16-byte alignment?  floatobject.c could use this API to avoid the 33% overhead.

The new obmalloc API could initially be internal use only until we can come up with a design we know we can live with long term.
Date User Action Args
2019-05-22 00:02:56naschemesetrecipients: + nascheme, twouters, gregory.p.smith, pitrou, vstinner, benjamin.peterson, methane, skrah, fweimer, tgrigg
2019-05-22 00:02:56naschemesetmessageid: <>
2019-05-22 00:02:56naschemelinkissue27987 messages
2019-05-22 00:02:56naschemecreate