[SciPy-user] scipy on old CPU crashes

oyster lepto.python@gmail....
Tue Dec 2 01:36:12 CST 2008

sorry, but scipy-0.7.0b1-win32-superpack-python2.4.exe and
numpy-1.2.1-win32-superpack-python2.4.exe crash on my old pc too,
which uses duron 750MHz. So now I think it is not the problem with
non-sse/sse/sse2 instruction

is there any method to find out the real reason except to compile from
the source


(I know Duron is too old, but currently I don't have the money to buy
a new PC or even update it :( so bad)

from scipy.integrate import quad
print quad(lambda x:x, 1, 2)      #crash soon

> Date: Thu, 13 Nov 2008 12:41:33 +0900
> From: "David Cournapeau" <cournape@gmail.com>
> Subject: Re: [SciPy-user] scipy on old CPU crashes
> To: "SciPy Users List" <scipy-user@scipy.org>
> Message-ID:
>        <5b8d13220811121941va8442f2gcb3a997874878b4b@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> On Thu, Nov 13, 2008 at 12:16 PM, oyster <lepto.python@gmail.com> wrote:
> > hi, all
> > I am using an old AMD Duron CPU with Win2k, which seems does not
> > support SSE/SSE2
> indeed, old Duron does not support SSE IIRC.
> > I found that there are 3 verisons in
> > numpy-1.2.1-win32-superpack-python2.5.exe(numpy-1.2.1-sse3.exe,
> > numpy-1.2.1-sse2.exe and numpy-1.2.1-nosse.exe)
> Yep, the superpack is just a simple wrapper around the correct
> installer, nothing fancy.
> > Is there a precompiled scipy that judges nosse/sse/sse2 automatically?
> No, but there will be for 0.7, which hopfully is only days away now.
> > or is there a way to
> > change ATLAS only according to my CPU?
> Unfortunately not without rebuilding scipy yourself. Win32 binaries
> are built by linking atlas statically.
> David

More information about the SciPy-user mailing list