[Numpy-discussion] Compiler change for Windows version between 220.127.116.11 and 1.0.4?
Wed Dec 19 19:35:35 CST 2007
Sounds like exactly the problem Jarrod Millman is working to solve.
The new binary uses SSE2 options which P3's and older Athlons don't
support. It sounds like Jarrod has found a machine he can use to
create the new binaries and solve the problem.
On Dec 18, 2007 1:07 PM, Stuart Brorson <firstname.lastname@example.org> wrote:
> Hi --
> I have found a bug in numpy-1.0.4. The bug is a crash when doing
> linalg.inv() on a Windows machine. The machine is an old Pentium 3
> machine. The error report indicates an invalid op code. Details
> about this bug are in the numpy tracker under ticket 635.
> Numpy-18.104.22.168 doesn't crash when running the same code.
> I installed the pre-built binaries available from numpy's SF site.
> Since the binaries were built by you, I can only suspect that the
> problem involves using a different compiler to build 1.0.4. I suspect
> the new version was built with a compiler which emitted op codes the
> old P3 chip couldn't handle.
> Can the developers confirm or deny my hypothesis?
> Stuart Brorson
> Interactive Supercomputing, inc.
> 135 Beaver Street | Waltham | MA | 02452 | USA
> Numpy-discussion mailing list
More information about the Numpy-discussion