Compiler change for Windows version between 1.0.3.1 and 1.0.4?
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-1.0.3.1 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? Thanks, Stuart Brorson Interactive Supercomputing, inc. 135 Beaver Street | Waltham | MA | 02452 | USA http://www.interactivesupercomputing.com/
Stuart Brorson 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-1.0.3.1 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?
You are correct, and the problem is in the process of being rectified by building on a different machine. There are several Trac tickets already posted due to this problem. -Travis O.
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 <sdb@cloud9.net> 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-1.0.3.1 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?
Thanks,
Stuart Brorson Interactive Supercomputing, inc. 135 Beaver Street | Waltham | MA | 02452 | USA http://www.interactivesupercomputing.com/ _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
participants (3)
-
Ryan Krauss -
Stuart Brorson -
Travis E. Oliphant