Bug in octave 3.2.x with custom atlas multithread

[Jaroslav Hajek]

On Fri, Jul 3, 2009 at 10:34 AM, Riccardo
Corradini<riccardocorradini at yahoo.it> wrote:
> Dear stuff,
> this is the bug report
>
> Subject: obench.m crashes with octave3.2.x multithreaded
> --------
> Bug report for Octave 3.2.1 configured for x86_64-unknown-linux-gnu
>
> Description:
> -----------
>
>   when I run the file obench.m available at
> http://www.reimeika.ca/marco/obench
> it crashes during complex operations
> Repeat-By:
> ---------
>
> I think there are problems with Fortran complex numbers libs
> NB : the make check gives no errors ( 0 FAILS)
> Fix:

It works for me, also on x86_64 (Core 2 Duo) Linux with GCC and
GotoBLAS on both -O3 -march=native and -O0 -g, and also with Intel
C++/Fortran and the multithreaded ACML library. I therefore suspect a
problem in your configuration, possibly miscompiled ATLAS (?). To
proceed further, I suggest you isolate the failure as narrowly as you
can, and run Octave with valgrind (when compiled, you can use
./run-octave -valgrind in the build dir) to find out whether the fault
occurs inside ATLAS or elsewhere.

Btw., I think -llapack should be specified *after* ATLAS, because
ATLAS optimizes some LAPACK subroutines and in this manner you
probably link to the unoptimized ones from within Octave. It may also
be the source of the crash, but I wouldn't bet on it.

cheers

-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz