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 fweimer
Recipients fweimer, gregory.p.smith, skrah, twouters, vstinner
Date 2018-01-31.10:55:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
max_align_t is a bit of a kitchen sink and will specify larger and larger alignment in the future, e.g. 32-byte alignment for a complex _Float128 type (a pair of two _Float128 variables).  The alignment is also not generally useful for allocations whose size is smaller than the alignment.  (Many mallocs do not follow the C standard and do not provide 16-byte alignment when 8 bytes are allocated, although alignof(max_align_t) is 16.)
Date User Action Args
2018-01-31 10:55:10fweimersetrecipients: + fweimer, twouters, gregory.p.smith, vstinner, skrah
2018-01-31 10:55:10fweimersetmessageid: <>
2018-01-31 10:55:10fweimerlinkissue31912 messages
2018-01-31 10:55:10fweimercreate