Commit Graph
72 Commits
Author SHA1 Message Date
igor175 5efe1971ec added new 'SR' test path (that sorresponds to symmetric indefinite factorization routines with rook pivoting) to the alahd.f routine that prints header information for different test paths 2011-12-25 01:18:39 +00:00
igor175 af570da6d5 added rook pivoting routines to the tests that check error exits for symmetric indefinite factorization routines, i.e. to serrsy.f derrsy.f cerrsy.f zerrsy.f 2011-12-25 01:15:10 +00:00
igor175 907d76cce5 added a comment to schksy.f cchksy.f dchksy.f zchksy.f 2011-12-24 01:49:37 +00:00
igor175 1d12a003eb updated comments and changed the way how test type counter NT is incremented in cchksy.f zchksy.f dchksy.f schksy.f 2011-12-23 23:54:32 +00:00
igor175 72b3274ec9 added *lavsy_rook.o and *zsyt01_rook.o to TESTING/LIN/Makefile 2011-12-23 05:38:47 +00:00
igor175 b6a857fdec chenge parameter ONE to CONE for complex routines clavsy.f, zlavsy.f. Also updated the documentation for these files to DoXigen format. Is seems that the documentation for these complex routines was not converted complely into DoXigen 2011-12-23 05:25:17 +00:00
igor175 2fd1c8f3df updated the documentation for dlavsy.f slavsy.f 2011-12-23 05:21:36 +00:00
igor175 ac3183fcd5 added slavsy_rook.f dlavsy_rook.f clavsy_rook.f zlavsy_rook.f 2011-12-23 05:00:52 +00:00
igor175 473b0bb127 added dlavsy_rook.f 2011-12-23 03:23:11 +00:00
igor175 db71b247d6 changed the order of external function declarations from CLAVSY, CLASET to CLASET, CLAVSY in csyt01.f to be consistent with zsyt01.f 2011-12-23 01:56:14 +00:00
igor175 fa41f57d3d changed the order of external function declarations from SLAVSY, SLASET to SLASET, SLAVSY in ssyt01.f to be consistent with dsyt01.f 2011-12-23 01:55:44 +00:00
igor175 9a3b0c2ffe added ssyt01_rook.f csyt01_rook.f zsyt01_rook.f 2011-12-23 01:52:04 +00:00
igor175 4ed2e4f235 added dchksy_rook.f 2011-12-23 01:50:30 +00:00
igor175 161689ad28 added 2011-12-23 01:16:22 +00:00
igor175 355cdb3ae1 added a few comments to the code in files for linear equations testing routines: schksy.f dchksy.f cchksy.f zchksy.f 2011-12-23 01:00:25 +00:00
igor175 6cc04f348a inserted a comment line '' into cchksy.f, zchksy.f, dchksy.f, schksy.f 2011-12-21 21:12:13 +00:00
igor175 11ecff3e7b corrected a typo from the previos commit: CALL pwd( PATH, NOUT ) replaced by CALL DERRSY( PATH, NOUT ) 2011-12-21 06:49:03 +00:00
igor175 939b459767 Included a comment about what CALL XLAENV( 2, 2 ) does in dchksy.f, schksy.f 2011-12-21 06:26:11 +00:00
igor175 9a0911c945 pached the comments blocks for test programs for linear equation routines schkaa.f dchkaa.f zchkaa.f cchkaa.f; added a description of MATMAX parameter, ann changed the description from 'Arguments' into 'Parameters' 2011-12-21 03:26:47 +00:00
igor175 272f202132 pached the comments blocks for test programs for linear equation routines schkaa.f dchkaa.f zchkaa.f cchkaa.f; inconsistency in the number of lines of the driver datafile 2011-12-21 01:03:29 +00:00
julie 3076651009 Fix bug bug0088 reported by Mike Pont from NAG on the forum
(see http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=2893)

This is related to the LAPACK-XBLAS routine: zherfsx.f

Here is what I did:
 - Introduce IINFO so that INFO is not overwritten
 - Use IGNORE_CWISE as suggested to prevent use of unitialize variable PARAMS
But this did not fix the problem reported.
INFO has new value in ZHERFSX (see description of INFO between ZHESVX and ZHESVXX)
This is set on line 634 (IF ( INFO .LE. N ) INFO = N + J) of zherfsx.f
And this is not handled by the testing LIN/zdrvhex.f
I just add  .AND. INFO.LE.N at line 638 to avoid raising an error when INFO = N + J

Please send feedback as I am not sure this is the best way to fix the issue.
I will commit other precision once fix approved.
Thanks
Julie
2011-12-10 06:45:16 +00:00
julie 758888bfa2 Modif call from xLA_RPVGRW to xLA_GERPVGRW
Routien Name was modified before.
2011-12-10 03:06:35 +00:00
langou 19cd29a4fb Change RWORK description in the header. The RWORK array needs to be at least of
dimension 2*NMAX to accomodate the calls to CHESVXX in CDRVHEX, ZHESVXX in
ZDRVHEX, CSYSVXX in CDRVSYX, and ZSYSVXX in ZDRVSYX. (The dimension of RWORK in
the caller subroutines --, e.g., ZCHKAA -- is way large enough.)
2011-11-30 16:17:35 +00:00
langou c428e19df0 Patching LAPACK testing routines according to Mike Pont (NAG)'s forum post #2894.
http://icl.cs.utk.edu/lapack-forum/viewtopic.php?t=2894
2011-11-30 13:34:58 +00:00
igor175 aa7f417d78 fixed new lines in testing drivers source files 2011-11-22 03:04:51 +00:00
julie 84118d4efb Update version number to 3.4.0 2011-11-11 19:34:11 +00:00
julie 1c3ba60067 Cosmetic changes in Doxygen presentation.
Use \par instead of \details for section.

add a Contributors Section and a Reference Section.
Remove (some) verbatim section when not needed.
Those changes have been done by hand so I am not sure I manage to catch them all.
2011-11-03 20:32:56 +00:00
julie d5c30c90bd Never say never... 2011-11-01 22:02:31 +00:00
julie 0d9e213c67 Correct Warning detected during Doxygen Generation.
Now each routine should have the correct list of arguments.
This allowed to detect and fix problems in parameter description of many routines.
2011-10-31 22:21:11 +00:00
julie a3ddf2b657 correction error checkers for sysv, posv, hesv, gbsv - reported by Nadezhda Mozartova (INTEL) 2011-10-25 07:17:15 +00:00
julie 4633d45bf3 add name of the routine before call 2011-10-25 07:05:50 +00:00
julie 11d2537893 Skip n=0 for rfp test to protect against div by zero - reported by Ake Sandgren on Oct 22nd on lapack mailing list 2011-10-25 07:01:05 +00:00
julie fba1a13c7e Fix Problem in testing discovered with the LAPACK dashboard related to rev 983 2011-10-07 09:46:30 +00:00
julie e1d39294ae Integrating Doxygen in comments 2011-10-06 06:53:11 +00:00
julie 420085d7a5 Add the LAPACK library as dependencies for testing after Igor's comment.
This means that if you change one file, all testings will be rerun.

Should we be smarter than that?
2011-09-26 21:52:31 +00:00
julie 55890ddab9 Improve CMAKE BUILD system and OUTPUT PARSING when not all precisions are needed.
The following variables will control the precision to be built:
  BUILD_SINGLE
  BUILD_DOUBLE
  BUILD_COMPLEX
  BUILD_COMPLEX16

For mixed precision SINGLE/DOUBLE routines, both BUILD_SINGLE and BUILD_DOUBLE needs to be on.
(same for COMPLEX/COMPLEX16)
2011-09-23 19:50:27 +00:00
julie 46e1b19474 Commit patch sent by Sven.
Patch was based on 3.3.0, so required a little bit of merging.
Thank you Sven for the corrections.
Julie



JL
TESTING/EIG
zerrgg.f
Declare ILO, IHI

SRC
---
I have corrected all the following warnings and errors:

c/d/s/zsysv.f, Unused external reference ILAENV
>JL OK
c/d/s/zsysv.f, Unused local variable NB
>JL  ALREADY CORRECTED

sgsvj0.f, Unused intrinsic AMIN1
> JL OK

d/sorbdb.f, Unused intrinsic MIN
> JL OK

sorcsd.f, Unused intrinsic SIN
sorcsd.f, Unused intrinsic COS
> JL OK MERGE

cpoequb.f, Unused intrinsic AIMAG
cpoequb.f, Unused intrinsic REAL
cpoequb.f, Unused local variable ZDUM

zgeequb.f, REAL --> DBLE
> JL OK

sorcsd.f, line 330: Inconsistent data type REAL (previously INTEGER) for argument 14 in reference to SORBDB
sorcsd.f, line 340: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGQR
sorcsd.f, line 345: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGQR
sorcsd.f, line 356: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGLQ
sorcsd.f, line 363: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGLQ
sorcsd.f, line 369: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGLQ
sorcsd.f, line 374: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGLQ
sorcsd.f, line 385: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGQR
sorcsd.f, line 392: Inconsistent data type REAL (previously INTEGER) for argument 4 in reference to SORGQR
sorcsd.f, line 399: Inconsistent data type REAL (previously INTEGER) for argument 9 in reference to SBBCSD
> JL OK MERGE


ila(s/d/c/z)lr.f
In the WHILE loop, at about line 59 I inserted
IF (I.EQ.0) THEN
   EXIT
END IF
since, otherwise when I = 0, A(0,J) is referenced.
> JL OK

TESTING/MATGEN
--------------
s/dlatm7.f
line 187: I replaced
IF( N.GT.1 ) THEN
by
IF( N.GT.1 .AND. RANK.GT.1 ) THEN
Otherwise I get a division by zero.
> JL OK

s/dlaror.f
I moved:
INFO = 0
from line 125 to line 121 in front of
 IF( N.EQ.0 .OR. M.EQ.0 )
$   RETURN
otherwise INFO is not defined on return when N or M are zero.
Similar change for
c/zlaror.f
> JL OK

TESTING/LIN
-----------
s/derrsy.f
In calls to S/DSYTRI2: I replaced IW by IW(1) since the dummy argument
(LWORK) is a scalar.
> JL OK

c/zerrrfp.f
I made ALPHA and BETA REAL/DOUBLE and introduced COMPLEX/COMPLEX*16
CALPHA since calls to C/ZHFRK need real alpha and beta.  In calls to
CTFSM, I then replaced ALPHA with CALPHA.
In cerrrfp.f, I replaced 1.0D0 with 1.0E0 (not strictly necessary, but
cleaner).
> JL OK

dpot06.f
Removed the unused declaration of LSAME
> JL OK

d/zdrvac.f
Removed the unused declaration of LSAME
> JL OK MERGE

s/d/c/z/ckcsd.f
Removed the unused declarations of S/D/C/ZLANGE, SIN and COS
> JL OK

c/zgennd.f
Removed the unused variable OUT
> JL already DONE

Corrected the following warnings and errors:

dchksy.f, Unused local variable MYWORK
> JL already DONE

ddrvgbx.f, line 792: Different number of arguments from the first call of DGBT02
> JL OK

cdrvgbx.f, line 726: Inconsistent data type REAL (previously COMPLEX) for argument 4 in reference to CLASET
cdrvgbx.f, line 728: Inconsistent data type REAL (previously COMPLEX) for argument 4 in reference to CLASET
cdrvgbx.f, line 780: Inconsistent data type REAL (previously COMPLEX) for argument 10 in reference to CGBT01
cdrvgbx.f, line 794: Different number of arguments from the first call of CGBT02
> JL OK

zdrvgbx.f, line 726: Inconsistent data type DOUBLE PRECISION (previously COMPLEX(KIND(0d0))) for argument 4 in reference to ZLASET
zdrvgbx.f, line 728: Inconsistent data type DOUBLE PRECISION (previously COMPLEX(KIND(0d0))) for argument 4 in reference to ZLASET
zdrvgbx.f, line 780: Inconsistent data type DOUBLE PRECISION (previously COMPLEX(KIND(0d0))) for argument 10 in reference to ZGBT01
zdrvgbx.f, line 794: Different number of arguments from the first call of ZGBT02
> JL OK

TESTING/EIG
-----------
s/d/c/zchkee.f
I inserted
CALL XLAENV( 12, 1 )
at line 1208, since IPARMS(ISPEC) with ISPEC = 12 needs to be set.
(I think I had to do this with them all, certainly with zchkee.f)
> JL OK zchkee.f cchkee.f

c/zchkee.f
In line 2316, the 15th argument of C/ZCKCSD should be real, not complex,
so I replaced A(1,7) by RWORK.
> JL OK

c/zcsdts.f
In calls to C/ZHERK I have replaced ONE by REALONE as arguments 5 and 8
should be real.
> JL OK

s/d/c/zcsdts.f
Division by zero occurs at line 155 in computing EPS when M = 0, so I
have modified
 EPS2 = MAX( ULP, CLANGE( '1', M, M, WORK, LDX, RWORK ) / REAL( M ) )
to
 IF (M.GT.0) THEN
    EPS2 = MAX( ULP, 
$               CLANGE( '1', M, M, WORK, LDX, RWORK ) / REAL( M ) )
 ELSE
    EPS2 = ULP
 END IF
> JL OK

SRC/VARIANTS/lu/CR
------------------
s/d/c/zgetrf
Removed the unused intrinsic MOD
> JL OK
2011-09-23 15:26:46 +00:00
julie 839c47632c Commit pb in TESTING reported by Nadezhda (INTEL) on Aug 29th.
"We notice that errorcheckers tests aren’t correct in some cases.
errorcheckers of ?ggevx, ?pstrf, ?pstf2
Some output parameters are read only in the errorcheckers tests."
2011-08-30 15:24:06 +00:00
julie 095393a41c Correct Bug in the testing of CHERFSX function
reported by omitrofa (olga.mitrofanova@intel.com)
See Forum 2644

Test of CHERFSX function doesn't work because there is an error
in ../TESTING/LIN/cerrhex.f ( lines 284-330 ). 
This function uses the diagonal pivoting factorization of a Hermitian
indefinite matrix instead of the diagonal pivoting factorization of
a Hermitian indefinite packed matrix. When CHERFSX is included in
conditional "IF( LSAMEN( 2, C2, 'HE' ) ) THEN " the test works.
2011-08-15 20:53:17 +00:00
james 830433cc32 test routines for new QRT subroutines:
xQRT04 tests xGEQRT and xGEMQRT
xQRT05 tests xTPQRT and xTPMQRT
2011-08-11 22:29:16 +00:00
julie b39d1348c9 First try to get a nice script to analyze the LAPACK testing.
Below is the help that goes with it.
Please send feedback. I tired to include several levels of output and several kind of errors
So far, I just tested it on my machine, that has no major problems.
I just tested "numerical errors", not "illegal error" neither "info error".

The goal is to have our nightly testing use it and also users.

TO DO:
  - Test other kinds of errors on machines
  - See to include it in ctest and buildbot (need to contact Don and Brad/Chuck)
  - See if a type of error option is required.


./lapack_testing.py [-h|--help] [-s |--short] [-f |--file] [-e |--error] [-p p |--prec p] [-t test |--test test] [-n | --number]
     - h is to print this message
     - f is to use directly the output of the LAPACK testing (.out files). By default, the script will run all the LAPACK tests
 LEVEL OF OUTPUT
     - x is to print a detailed summary
     - e is to print only the error summary
     - s is to print a short summary
     - n is to print the numbers of failing tests (turn on summary mode)
 SECLECTION OF TESTS:
     - p [s/c/d/z] is to indicate the PRECISION to run:
            s=single
            d=double
            c=complex
            z=double complex
            x=all [DEFAULT]
     - t [lin/eig/mixed/rfp/all] is to indicate which TEST FAMILY to run:
            lin=Linear Equation
            eig=Eigen Problems
            mixed=mixed-precision
            rfp=rfp format
            all=all tests [DEFAULT]
 EXAMPLES:
     ./lapack_testing.py -n -f
            Will return the numbers of failed tests by analyzing the LAPACK output
     ./lapack_testing.py -n -f -p s
            Will return the numbers of failed tests in REAL precision by analyzing the LAPACK output
     ./lapack_testing.py -n -f -p s -t eig 
            Will return the numbers of failed tests in REAL precision by analyzing only the LAPACK output of EIGEN testings
Written by Julie Langou (June 2011)
2011-06-24 08:46:19 +00:00
julie 0d0b443c69 Summer cleanup
Cleanup some codes, like unused variables.
Used -Walls to detect problems.
2011-06-22 09:45:40 +00:00
julie dd795d2903 Upadte header for the modified routine for the 3.3.1 release 2011-04-13 16:30:39 +00:00
julie adc144b1c1 Correct and Add Error exit tests for *errtz
Test the case where N=M (Workspace should be 1), so put LWORK at 0 to make it failed
Test the case where N!=M (Workspace should be more than MAX(1,M)), so put M=2, N=3 ans LWORK at 1 to make it failed

Correct some typos in [dz]drgsx testings.
2011-03-03 23:13:58 +00:00
julie 7847ac8fb5 Wrapped lines that extended past 72 columns
- Chuck Atkins (Kitware)
2011-02-28 03:42:25 +00:00
julie d1e13ae046 Adding new hetri routines 2011-01-20 17:33:46 +00:00
julie e057a1ba80 Suppress warning because of undefined variable 2011-01-11 14:10:14 +00:00
julie bf1f0449f1 Fix line length 2010-11-17 22:57:18 +00:00
julie f084f12180 Start getting ready for the release 2010-11-08 20:15:23 +00:00
julie 1237a0d5b7 Commiting the 3 other precisions (single, complex, dcomplex) for sytri using Level BLAS 3.
Update testing accordingly
2010-11-03 17:55:43 +00:00