Possible error in ZGBSVX testing

Post here if you want to report a bug to the LAPACK team

Possible error in ZGBSVX testing

Postby tkoenig » Sat Jan 07, 2012 5:53 am

Hello,

I want to set up a regression tester for gfortran in Lapack, i.e.

- Download the latest gcc/gfortran version
- compile it
- Compile Lapack with the new compiler
- Test Lapack
- Send the results to the gcc-testresults mailing list

The machine is a power7 from the gcc compile farm http://gcc.gnu.org/wiki/CompileFarm

In setting this up, I found error messages like

*** On entry to ZGBSVX parameter number 13 had an illegal value ***
*** On entry to ZGBSVX parameter number 13 had an illegal value ***
*** On entry to ZGBSVX parameter number 13 had an illegal value ***
*** On entry to ZGBSVX parameter number 13 had an illegal value ***

...
*** On entry to ZGBSVX parameter number 14 had an illegal value ***
*** On entry to ZGBSVX parameter number 14 had an illegal value ***
*** On entry to ZGBSVX parameter number 14 had an illegal value ***
*** On entry to ZGBSVX parameter number 14 had an illegal value ***

Other architectures to not appear to show this problem. I have sumitted this as a bug against gcc, in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51751 The (fairly limited) analysis I have done can be found in the audit trail of that bug.

I am not sure if this is a gcc bug, or a bug in testing that only shows up on specific architectures, which is why I am reporting it here.
tkoenig
 
Posts: 2
Joined: Sat Jan 07, 2012 5:38 am

Re: Possible error in ZGBSVX testing

Postby admin » Sun Jan 08, 2012 1:28 am

Hi,
could you post the whole error output so that we try reproducing your problem.
Also please post your compilation flags.
Thanks
Julie
admin
Site Admin
 
Posts: 504
Joined: Wed Dec 08, 2004 7:07 pm

Re: Possible error in ZGBSVX testing

Postby tkoenig » Sun Jan 08, 2012 6:07 am

Hi,

the error occurred independent of optimization level.

Here are the current options (the -static is still a leftover from prvious testing,
makes no difference) from make.inc:

FORTRAN = ~/bin/gfortran
OPTS = -O0 -g
DRVOPTS = $(OPTS)
NOOPT = -O0 -static
LOADER = ~/bin/gfortran
LOADOPTS =

~/bin/gfortran -v is

Using built-in specs.
COLLECT_GCC=/home/tkoenig/bin/gfortran
COLLECT_LTO_WRAPPER=/home/tkoenig/libexec/gcc/powerpc64-unknown-linux-gnu/4.7.0/lto-wrapper
Target: powerpc64-unknown-linux-gnu
Configured with: ../trunk/configure --prefix=/home/tkoenig --enable-languages=c,fortran
Thread model: posix
gcc version 4.7.0 20120104 (experimental) (GCC)

Also fails with

Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/ppc64-redhat-linux/4.6.2/lto-wrapper
Target: ppc64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,lto --enable-plugin --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --enable-secureplt --with-long-double-128 --build=ppc64-redhat-linux
Thread model: posix
gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC)

Output is attached (took me some time to find out I had to gzip it...)

If there is anything more I can do, please let me know.
Attachments
ztest.out.gz
gzipped output of xlintstz < ztest.in
(20 KiB) Downloaded 49 times
tkoenig
 
Posts: 2
Joined: Sat Jan 07, 2012 5:38 am


Return to Bug report

Who is online

Users browsing this forum: No registered users and 1 guest