Xref: utzoo sci.math.stat:1379 comp.sources.wanted:11891 sci.math.num-analysis:840
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!aries!mcdonald
From: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Newsgroups: sci.math.stat,comp.sources.wanted,sci.math.num-analysis
Subject: Re: LINPACK and EISPACK in C
Keywords: translation, fortran - C source, linear algebra, eigensystems
Message-ID: <1990May27.231957.8019@ux1.cso.uiuc.edu>
Date: 27 May 90 23:19:57 GMT
References: <1990May25.004501.25148@athena.mit.edu> <1990May27.221236.8978@athena.mit.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Organization: School of Chemical Sciences, Univ. of Illinois at Urbana-Champaign
Lines: 13

I have just two of the Eispack routines - tred2 and tql2 - in C
somewhere or other. 

They are not pretty to look at. These routines are an excellent
example of why one needs to be able to write 2-D arrays in array
notation inside functions.  I have pointerized the inner loops and
use [i*n+j] for the outer loops.

On our MIPS 2000 the C versions run very much faster than the Fortran
ones, due to a lapse in MIPS's Fortran optimizer. On a 386 PC they
are only a little faster.

Doug McDonald(mcdonald@aries.scs.uiuc.edu)