Commit Graph
15 Commits
Author SHA1 Message Date
Mark Gates 62b1d4a032 implicit none in TESTING/LIN 2025-08-26 23:27:58 -04:00
musvaage f3fff11ccf typos 2023-04-11 13:52:58 -05:00
Igor Zhuravlov 1825be67cf fixed comments: specify which norm is used (no.1 from PR #562)
Despite the recommendation, no change has been made in xGBT02, xGET02, xGTT02, xTBT02, xTPT02,
and xTRT02 for C,Z datatypes yet: as it was noted afterwards in PR #571, those routines are
using mixed types of norm: 1-norm for op(A) and taxicab-based norm |Re(z)|+|Im(z)| for residual.
2021-06-09 22:01:03 +10:00
Igor Zhuravlov a98ffc640d comments unified: specify where result will be stored in xGBT01 and xPOT01
Were unified with xGET02, xGET08, xPOT06, xQRT16, xSYT02.
2021-06-03 23:01:38 +10:00
Igor Zhuravlov 2f9f42bf2c comments unified and enhanced: TRANS parameter 2021-06-03 23:00:25 +10:00
Igor Zhuravlov 457afcf7df comments unified: homgenize notation for transpose (**T) and conjugate transpose (**H)
This commit continues changes made in:
* Reference-LAPACK/lapack@f2953573ed 2011-04-02
* Reference-LAPACK/lapack@d9d50d133b 2011-04-02
* Reference-LAPACK/lapack@16973f0c15 2011-04-08
2021-06-03 22:59:29 +10:00
Igor Zhuravlov 6d69cc317f comments fixed: synced with code in xGTT02 (#3 from PR#562)
Comments in xGTT02 declared that it uses norm(A) but its code implemented 1-norm of op(A).
2021-05-24 10:18:45 +10:00
Julie e18d437924 Making LAPACK's code eternal... no more version and date in source files.
GitHub is now enabling us to track accurately version and date.
No need for this anymore.
2021-03-25 10:16:58 -07:00
Julie bc6a755be4 Updating version number on source file modified since 3.6.1
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-12-23 15:01:32 -08:00
Hans Johnson 9dafba6d41 STYLE: Remove trailing whitespace in Fortran files
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
=================================================
2016-07-09 11:19:34 -05: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 e1d39294ae Integrating Doxygen in comments 2011-10-06 06:53:11 +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
jason baba851215 Move LAPACK trunk into position. 2008-10-28 01:38:50 +00:00