On Dec 21, 2007 9:40 AM, Charles R Harris <[EMAIL PROTECTED]> wrote:
>
>
>
>
> On Dec 20, 2007 9:32 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > > > when compiled on Debian, numpy segfaults when used with ATLAS sse2,
> > > > but works when used against ATLAS sse. More information here:
> > >
>
On Dec 20, 2007 9:32 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > > when compiled on Debian, numpy segfaults when used with ATLAS sse2,
> > > but works when used against ATLAS sse. More information here:
> >
> > What is the machine on which you are getting the segfault? Is it
>
> I don't know
to, 2007-12-20 kello 17:32 +0100, Ondrej Certik kirjoitti:
> > > when compiled on Debian, numpy segfaults when used with ATLAS sse2,
> > > but works when used against ATLAS sse. More information here:
> >
> > What is the machine on which you are getting the segfault? Is it
>
> I don't know which
> > when compiled on Debian, numpy segfaults when used with ATLAS sse2,
> > but works when used against ATLAS sse. More information here:
>
> What is the machine on which you are getting the segfault? Is it
I don't know which machine the reporter of this bug in Debian uses, but I use
Intel Core D
Hi,
> when compiled on Debian, numpy segfaults when used with ATLAS sse2,
> but works when used against ATLAS sse. More information here:
What is the machine on which you are getting the segfault? Is it
possible you are trying to run SSE2 instructions on a machine without
SSE2?
Best,
Matthew
_
Hi,
when compiled on Debian, numpy segfaults when used with ATLAS sse2,
but works when used against ATLAS sse. More information here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448530
I have no idea, where the problem is. Do you have any ideas, what we should try?
Thanks a lot,
Ondrej
___
