[Numpy-discussion] Scipy 0.15.0 beta 1 release

Nathaniel Smith njs at pobox.com
Wed Nov 26 11:46:32 EST 2014

On 26 Nov 2014 13:59, "Julian Taylor" <jtaylor.debian at googlemail.com> wrote:
> concerning actually fixing it I guess we have 3 options:
> 1. reduce maximum copy alignment from currently 16 to 8 on platforms
> that need it.
> That will automatically reduce the needed alignment of complex on win32
> to 8 bytes. Do other compilers provide something similar to gccs
> 2. remove bloating of complex alignment and let sparc crash.
> 3. add an aligned allocator
> I somewhat favor 1, it has the risk that a vectorizing compiler might
> wreak havoc but to my knowledge numpy does not actually have real 16
> byte copies. There are some occurrences of npy_int128, but those likely
> are not used on windows.
> fwiw I could reproduce the issue on linux i386 with -malign-double, (I
> could have sworn I tested that configuration too...)

I'm not sure what "maximum copy alignment" means in this context, but (1)
does sound the most like a proper fix to me too.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20141126/69a25dfe/attachment.html>

More information about the NumPy-Discussion mailing list