Hi Julian, On Mon, Feb 8, 2016 at 8:40 AM, Julian Taylor <jtaylor.deb...@googlemail.com> wrote: > On 02/08/2016 05:23 PM, Daπid wrote: >> >> On 8 February 2016 at 16:19, Olivier Grisel <olivier.gri...@ensta.org >> <mailto:olivier.gri...@ensta.org>> wrote: >> >> >> >> OPENBLAS_CORETYPE=Nehalem python3 -c "import numpy as np; from scipy >> import linalg; linalg.eigh(np.random.randn(200, 200))" >> >> So this is an issue with the architecture detection of OpenBLAS. >> >> >> I am seeing the same problem on a native Linux box, with Ivy Bridge >> processor (i5-3317U). According to your script, both my native openblas >> and the one in the wheel recognises my CPU as Sandybridge, but the wheel >> produces a segmentation fault. Setting the architecture to Nehalem works. >> > > more likely that is a bug the kernel of openblas instead of its cpu > detection. > The cpuinfo of Oliver indicates its at least a sandy bridge, and ivy > bridge is be sandy bridge compatible. > Is an up to date version of openblas used?
I used the latest release, v0.2.15: https://github.com/matthew-brett/manylinux-builds/blob/master/build_openblas.sh#L5 Is there a later version that we should try? Cheers, Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion