summaryrefslogtreecommitdiff
path: root/SRC/zla_hercond_x.f
AgeCommit message (Collapse)AuthorFilesLines
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-07-03Add Brief description for auxiliary routinesjulie1-1/+1
2012-04-12Follow up to rev r1130 julie1-2/+9
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) Actually there were a lot of problems regarding arguments checking. I tried to correct most of them. Apply the fix propose to all x[he/sy]rfsx.f routines - Use IGNORE_CWISE as suggested to prevent use of unitialize variable PARAMS I also appied the previous TESTING fix to all routines 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 At the moment, I would recommand a further look at those routines. ZHE, ZSY led to 182 Tests failing to pass the threshold and the same for complex better than before, but still....
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-56/+127
2011-04-07Second and hopefully last pass to homgenize notation for transpose (**T) and ↵julie1-1/+1
conjugate transpose (**H) Corresponds to bug0024 Please take a look and let me know if you find some old notation of transpose. I am going to close bug0024. Julie
2009-04-16Big commit before 3.2.1 release.julie1-2/+2
Those are just cosmetic changes to update version number and various other minor change.
2009-04-08Updated documentation for EPIR routines. Changed ERRS_{N,C} variable names. ↵deaglanhalligan1-5/+38
Other cosmetic changes.
2009-02-13Restructured loops in {c,z}la_yyrcond_{x,c} and {s,c,d,z}la_yyamv to do less ↵deaglanhalligan1-13/+11
comparisons.
2009-02-11Added Jasons patches to bring work and rwork down to 2*N in the complex ↵deaglanhalligan1-4/+4
refinement routines.
2008-12-30Merged revisions 609-614 via svnmerge from jason1-3/+16
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-0/+169