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 jtaylor
Recipients jtaylor, mapreri, methane, vstinner
Date 2017-05-23.10:03:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495533838.18.0.856947330163.issue30150@psf.upfronthosting.co.za>
In-reply-to
Content
no in numpy it is just a case of using the wrong allocator in a certain spot, an issue that can be fixed in numpy.
But it is also minor bug/documentation issue in Python itself.

Alignment isn't very important for SIMD any more but there are architectures where alignment is still mandatory so numpy is sprinkled with asserts checking alignment which triggered on x32.
It is a very minor issue as to my knowledge none of the platforms with alignment requirement has the properties of x32 and x32 doesn't actually care about alignment either.
History
Date User Action Args
2017-05-23 10:03:58jtaylorsetrecipients: + jtaylor, vstinner, methane, mapreri
2017-05-23 10:03:58jtaylorsetmessageid: <1495533838.18.0.856947330163.issue30150@psf.upfronthosting.co.za>
2017-05-23 10:03:58jtaylorlinkissue30150 messages
2017-05-23 10:03:58jtaylorcreate