summaryrefslogtreecommitdiff
path: root/SRC/ilazlr.f
AgeCommit message (Collapse)AuthorFilesLines
2016-12-23Updating version number on source file modified since 3.6.1Julie1-3/+3
This is really old school, but a lot of times we have users sending us copy pasting of codes, and that is the only way to know the version of the code.
2016-07-09STYLE: Remove trailing whitespace in Fortran filesHans Johnson1-15/+15
This is mostly a long term maintenance improvement. Many coding styles require elimination of trailing whitespace, and many editors and source code management configurations automatically gobble up whitespace. When these tools gobble up whitespace, it complicates reviewing the meaningful code changes. By removing whitespace on one patch, it makes future code reviews much easier. =SCRIPT==================================================================== if which tempfile &>/dev/null; then TEMPMAKER=tempfile elif which mktemp &>/dev/null; then TEMPMAKER=mktemp else echo "Cannot find tempfile program." 2>&1 exit 1 fi MYTEMP=$($TEMPMAKER) trap 'rm -f $MYTEMP' SIGINT SIGTERM stripit() { echo "stripping $1" sed 's/[ \t]*$//' "$1" > $MYTEMP cp $MYTEMP "$1" } if [ $# -gt 0 ]; then while [ "$1" != "" ]; do stripit $1 shift done else while read -t 2; do stripit $REPLY done fi rm $MYTEMP =================================================
2012-09-25(no commit message)julie1-2/+2
2012-08-25(no commit message)julie1-3/+3
2012-08-18reverting to previous version, which is correctjames1-1/+1
2012-08-17fixed logic error that corrects bug found by Duncan Po at Mathworksjames1-1/+1
2012-07-03Add Brief description for auxiliary routinesjulie1-1/+1
2012-04-13Update version numberjulie1-3/+3
2011-11-30fixed bug.james1-6/+3
2011-11-11Update version number to 3.4.0julie1-1/+1
2011-11-03Cosmetic changes in Doxygen presentation.julie1-13/+11
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-01Last commit related to Doxygen integration following Albert's commentjulie1-1/+3
2011-10-13adding link to individual download, the links will appear directly in ↵julie1-0/+8
Doxygen html documentation
2011-10-06Integrating Doxygen in commentsjulie1-21/+71
2011-09-23Commit patch sent by Sven.julie1-6/+6
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-04-21fixed problems with zero matrix and scanjames1-3/+6
2011-04-13Upadte header for the modified routine for the 3.3.1 releasejulie1-5/+2
2011-03-03replaced "do/exit" scan logic with do while loopjames1-3/+4
fixes bug0075 and bug0035
2010-06-23Update date and version for 3.2.2 releasejulie1-2/+2
2010-01-28Polish some comments, etc.. for the C wrapperjulie1-2/+2
2009-04-16Big commit before 3.2.1 release.julie1-3/+6
Those are just cosmetic changes to update version number and various other minor change.
2008-12-30Merged revisions 609-614 via svnmerge from jason1-41/+43
https://jason@icl.cs.utk.edu/svn/lapack-dev/lapack/branches/SC08-release ........ r609 | julie | 2008-12-16 17:17:52 -0500 (Tue, 16 Dec 2008) | 1 line Polish routines to fit the LAPACK framework and allow manpages generation ........ r610 | langou | 2008-12-19 12:12:38 -0500 (Fri, 19 Dec 2008) | 30 lines bug reported on the forum https://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=2&t=854 the complete thread is available at http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/635192e11beadb93# Tobias Burnus also sent us an email: > Hello, > > this was reported at > http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/635192e11beadb93# > > The problem is the line 47: > > 47: IF( M.EQ.0 .OR. A(M, 1).NE.ZERO .OR. A(M, N).NE.ZERO ) THEN > > If M == 0 the one accesses A(0,1) which is invalid as the lower bound is 1 > and not 0. > > Note: Contrary to C there is no left-to-right evaluation of expressions in > Fortran; the order is left to the compiler. One might assume that a smart > compiler does not evaluate "A(M,1)" if "M==0", however, there is nothing in > the standard guarantees this. > > If bounds checks are turned on (see post at the URL above), gfortran aborts > with an out-of-bounds error. ........ r611 | julie | 2008-12-19 15:00:58 -0500 (Fri, 19 Dec 2008) | 5 lines Modify the formatting of the comments. Replace Note and Notes section by Further Details This allow the manpages to be generated corectly. ........ r612 | julie | 2008-12-19 16:29:21 -0500 (Fri, 19 Dec 2008) | 3 lines Reformat the xblas routines comments to be able to generate the manpages ........ r613 | julie | 2008-12-19 16:30:31 -0500 (Fri, 19 Dec 2008) | 1 line Update version number ........ r614 | jason | 2008-12-27 09:44:45 -0500 (Sat, 27 Dec 2008) | 13 lines Fix non-short-circuited tests in ILAxL{C,R}. Fortran doesn't short-circuit logical operators, so the check that the leading dimension /= 0 may not prevent indexing into a 0-length array. Reported by "hes selex" in http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/635192e11beadb93 and forwarded to the LAPACK maintainers by Tobias Burnus <burnus@net-b.de>. Chalk up more bugs found by gfortran's diagnostics! Signed-off-by: Jason Riedy <ejr@cs.berkeley.edu> Cc: Tobias Burnus <burnus@net-b.de> ........
2008-12-16(no commit message)julie1-1/+1
2008-10-28Move LAPACK trunk into position.jason1-0/+60