On 26 Nov 2014 13:59, "Julian Taylor" <jtaylor.deb...@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 > __BIGGEST_ALIGNMENT__? > 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. -n
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
