octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GotoBLAS2 gives many FAILS on test of eigs.cc


From: John W. Eaton
Subject: Re: GotoBLAS2 gives many FAILS on test of eigs.cc
Date: Thu, 20 Jan 2011 06:25:52 -0500

On 20-Jan-2011, John W. Eaton wrote:

| On 20-Jan-2011, Fredrik Lingvall wrote:
| 
| | On 01/20/11 09:58, John W. Eaton wrote:
| | > On 20-Jan-2011, Fredrik Lingvall wrote:
| | >
| | > | I also have the issue that I need to change n from 200 to 100 in
| | > | doc/interpreter/sparseimages.m to make Octave build (see also
| | > | 
http://octave.1599824.n4.nabble.com/Octave-3-3-54-snapshot-available-for-ftp-td3051025.html)
| | > | 
| | > | It's configured with:
| | > | 
| | > | ./configure  CFLAGS="-O2 -pipe -march=native -pthread" \
| | > |          CXXFLAGS="-O2 -pipe -march=native -pthread" \
| | > |          LDFLAGS="-lgfortran" F77=gfortran \
| | > |          FFLAGS="-O2 -pipe -march=native -pthread" \
| | > |          F77_INTEGER_8_FLAG="-fdefault-integer-8" \
| | > |          --enable-64 --prefix=/usr/local/ \
| | > |          --with-blas=/usr/local/lib/libBLAS.so
| | > | --with-lapack=/usr/local/lib/libLAPACK.so --enable-shared
| | >
| | > And you built your copies of libBLAS.so and libLAPACK.so so that they
| | > also use 8-byte integers?
| | >
| | > jwe
| | Yes.
| | 
| | LAPACK is build with:
| | 
| | OPTS     = -O2 -march=native -fdefault-integer-8 -fPIC
| | 
| | and Goto BLAS with:
| | 
| | BINARY=64
| | 
| | and
| | 
| | INTERFACE64 = 1
| 
| To debug the problem, you can start by going to the test directory of
| your build tree and running
| 
|   ../run-octave -g --norc --silent --no-history $srcdir/fntests.m $srcdir
| 
| where $srcdir should be replaced by the name of the directory where
| the sources for the test directory are.  Then type
| 
|   b main
|   r
|   b error
|   b xstopx
|   c
| 
| at the (gdb) prompt.  Then when you get to the error about the bad
| parameter passed to DGEMV, you should end up back at the debug prompt,
| inside the xstopx_ or error function.  Then get a backtrace by typing
| 
|   where
| 
| at the gdb prompt and let us know where the call to DGEMV is (file and
| line number).  That might give a clue.

Also, are you sure you are linking to the correct libraries at run
time?  What does

  ./libtool --mode=execute ldd src/octave

tell you?

I'm able to build with --enable-64 and link with the reference
BLAS+LAPACK, both compiled with gfortran -fdefault-integer-8 and all
tests pass except one, the same one from data.cc that fails when I
build a 32-bit binary without optimization.

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]