David Cournapeau wrote:
Michael Abshoff wrote:
Hi David,
Sorry for not being precise: Both python and numpy have been build with
OPT=-DNDEBUG -g -O0 -fwrapv -Wall -Wstrict-prototypes
Hm, strange. I don't know why you can't get any debug info, then.
well, it looks like some sort of stack
Michael Abshoff wrote:
So it looks like gfortran 4.2.4 on Solaris + -O3 miscompiles lapack,
which is honestly unbelievable considering netlib.org lapack+BLAS are
the yard stick for any Fortran compiler.
Well, not many people use gfortran on Solaris, I would guess. Another
problem with
Michael Abshoff wrote:
This is python 2.5.2 build with gcc 4.2.4, numpy itself is build with
-O0, i.e. this is unlikely to be a compiler bug IMHO. This bug has
been present in 1.0.4, 1.1.0 and it seems unfixed in 1.2.rc1. The numpy
1.1 test suite passed with that install, I did not run the
David Cournapeau wrote:
Michael Abshoff wrote:
Hi David,
This is python 2.5.2 build with gcc 4.2.4, numpy itself is build with
-O0, i.e. this is unlikely to be a compiler bug IMHO. This bug has
been present in 1.0.4, 1.1.0 and it seems unfixed in 1.2.rc1. The numpy
1.1 test suite passed
Michael Abshoff wrote:
Sorry for not being precise: Both python and numpy have been build with
OPT=-DNDEBUG -g -O0 -fwrapv -Wall -Wstrict-prototypes
Hm, strange. I don't know why you can't get any debug info, then.
i.e. -O0 instead of -O3. I am using ATLAS and netlib.org Lapack, so
I
