You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In [2]: dot(eye(1000),eye(1000))
Illegal instruction
The products work for smaller arrays, so I suspect either the output array or a work array is being created with the wrong size, probably a 64bit integer thing in the cblas interface. The example works on 32 bit linux.
I think this may be an error in the ATLAS libraries. I am running fc5 here with the ATLAS libraries installed from extras repository, However, those rpms are generated from a script borrowed from Debian, so the problems are probably common to both. Anyway, the following c program also generates the error:
For Debian, I believe lib64 should be replaced by lib. Anyway, I think this is either a compiler or ATLAS problem that exhibits itself when the arrays get large enough to require blockiing or some such. I compiled with gcc version 4.1.1. The program works fine if 1000 is replaced by 10 everywhere.
I'm closing this ticket. I compiled ATLAS-3.7.30 for my machine and the test program ran successfully, so this is a problem with the distributed ATLAS libraries. I have filed a bug report with Fedora bugzilla. I suggest that someone who runs Debian or Ubuntu also file bug reports.
BTW, apart from the time, ATLAS-3.7.30 was pretty easy to compile. And the optimization time wasn't bad on this machine, either, < 30 minutes. Apart from that, I believe Whaley recommends using version 3.7 instead of 3.6 because the time between official stable releases has become so long.
Original ticket http://projects.scipy.org/numpy/ticket/497 on 2007-04-10 by @charris, assigned to unknown.
The problem is easy to exhibit:
The products work for smaller arrays, so I suspect either the output array or a work array is being created with the wrong size, probably a 64bit integer thing in the cblas interface. The example works on 32 bit linux.
This ticket replaces #1030
The text was updated successfully, but these errors were encountered: