|
|
@ -41,8 +41,8 @@ For the F77 compiler, we assume it supports DOUBLE COMPLEX and DO WHILE/ENDDO.
|
|
|
|
Practically all compilers do nowadays.
|
|
|
|
Practically all compilers do nowadays.
|
|
|
|
The compilation process relies on the choice of an appropriate
|
|
|
|
The compilation process relies on the choice of an appropriate
|
|
|
|
Make.inc file; we have tested with AIX XLF, Intel ifc/Linux, Lahey
|
|
|
|
Make.inc file; we have tested with AIX XLF, Intel ifc/Linux, Lahey
|
|
|
|
F95/Linux and Nag f95/Linux. If you succeed in compiling with other
|
|
|
|
F95/Linux, Nag f95/Linux, GNU Fortran/Linux. If you succeed in compiling with
|
|
|
|
compiler/operating systems please let us know.
|
|
|
|
other compiler/operating systems please let us know.
|
|
|
|
|
|
|
|
|
|
|
|
IBM SP2.
|
|
|
|
IBM SP2.
|
|
|
|
The library has been tested on an IBM SP2 with XLC and XLF
|
|
|
|
The library has been tested on an IBM SP2 with XLC and XLF
|
|
|
@ -59,28 +59,22 @@ LINUX:
|
|
|
|
|
|
|
|
|
|
|
|
There finally exist a GNU Fortran 95 implementation: we are using the
|
|
|
|
There finally exist a GNU Fortran 95 implementation: we are using the
|
|
|
|
development snapshots from GCC 3.5.0, later 4.1 and 4.2 since July
|
|
|
|
development snapshots from GCC 3.5.0, later 4.1 and 4.2 since July
|
|
|
|
2004, and it appears to work. This is on its way to become the
|
|
|
|
2004, and it appears to work. The 4.2 version of GNU compilers is now
|
|
|
|
reference platform.
|
|
|
|
our reference platform.
|
|
|
|
|
|
|
|
|
|
|
|
We compiled with egcs G77/GCC and mpich-1.2.0, 1.2.1, 1.2.2 and 1.2.4.
|
|
|
|
|
|
|
|
With some versions of GCC, g77 chokes on SRC/SERIAL/dcsdp.f; this
|
|
|
|
|
|
|
|
problem seems to have disappeared in recent GCC distributions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Vast F90/Linux is now obsolete, in that we have a NULL()
|
|
|
|
|
|
|
|
initialization for pointers that is outside strict F90.
|
|
|
|
Vast F90/Linux and PGI f90/Linux are now obsolete, in that we have a
|
|
|
|
|
|
|
|
NULL() initialization for pointers that is outsied strict F90; they
|
|
|
|
|
|
|
|
cannot be used any longer.
|
|
|
|
|
|
|
|
For the PGI compilers, we used them in conjunction with gcc, NOT
|
|
|
|
For the PGI compilers, we used them in conjunction with gcc, NOT
|
|
|
|
pgcc. Note that with pgi 3.6 we have horrible performance, due to
|
|
|
|
pgcc. Note that with pgi 3.6 we have horrible performance, due to
|
|
|
|
spurious array copies when calling Fortran 77 codes from Fortran 90;
|
|
|
|
spurious array copies when calling Fortran 77 codes from Fortran 90;
|
|
|
|
this is fixed in version 4.
|
|
|
|
this is fixed in version 4 and later.
|
|
|
|
|
|
|
|
|
|
|
|
The Lahey version we got access to (6.0 and 6.1) seems to suffer from
|
|
|
|
The Lahey version we got access to (6.0 and 6.1) seems to suffer from
|
|
|
|
the same extra copies problem; this is most apparent in the matrix
|
|
|
|
the same extra copies problem; this is most apparent in the matrix
|
|
|
|
build process.
|
|
|
|
build process.
|
|
|
|
|
|
|
|
|
|
|
|
For the Intel compilers, we used ifc version 7.0 and 7.1; with version 6.0
|
|
|
|
For the Intel compilers, we used ifc versions 7, 8 and 9; with version 6.0
|
|
|
|
you need to change the way modules are handled, but we recommend to migrate
|
|
|
|
you need to change the way modules are handled, but we recommend to migrate
|
|
|
|
to the new version anyway. Moreover, with versions prior to 7.1, there
|
|
|
|
to the new version anyway. Moreover, with versions prior to 7.1, there
|
|
|
|
is a strange error in pargen/ppde90: the compiler did not like the
|
|
|
|
is a strange error in pargen/ppde90: the compiler did not like the
|
|
|
@ -115,48 +109,9 @@ We have had good results with the METIS library, which can be
|
|
|
|
obtained from
|
|
|
|
obtained from
|
|
|
|
http://www-users.cs.umn.edu/~karypis/metis/metis/main.html
|
|
|
|
http://www-users.cs.umn.edu/~karypis/metis/metis/main.html
|
|
|
|
|
|
|
|
|
|
|
|
We include interfaces to: SuperLU 3.0 and UMFPACK 4.4.
|
|
|
|
We include interfaces to:
|
|
|
|
|
|
|
|
-- SuperLU 3.0 http://crd.lbl.gov/~xiaoye/SuperLU/
|
|
|
|
|
|
|
|
-- UMFPACK 4.4 http://www.cise.ufl.edu/research/sparse/umfpack/
|
|
|
|
|
|
|
|
|
|
|
|
NEW:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Reviewed the interfaces: in the tools section we really need the
|
|
|
|
|
|
|
|
POINTER attribute for dense vectors, but not in the computational
|
|
|
|
|
|
|
|
routines; taking it out allows more flexibility. Besides, this acts
|
|
|
|
|
|
|
|
as a workaround for a bug on Linux/VAST: as of version
|
|
|
|
|
|
|
|
"vf90 Personal V3.4N5" the DOT and NRM functions had to be
|
|
|
|
|
|
|
|
transformed into subroutines whenever the vectors had the POINTER
|
|
|
|
|
|
|
|
attribute; now both subroutine and function versions work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Added more methods: CGS, BiCGSTAB(L), BiCG
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- We now have a new Preconditioner F90 routine; diagonal scaling works
|
|
|
|
|
|
|
|
with COO, CSR and JAD; ILU works with JAD, but is more expensive in terms
|
|
|
|
|
|
|
|
of memory space
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- We added some extensions to compute multiple DOTs and AMAXs at once;
|
|
|
|
|
|
|
|
they can be useful in solving vector equations (e.g. momentum
|
|
|
|
|
|
|
|
equation in fluid dynamics).
|
|
|
|
|
|
|
|
- Halo data exchange in F90_PSHALO can now be applied to integer data;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- There is an update capability for cases where the same sparsity
|
|
|
|
|
|
|
|
pattern is reused (e.g. multiple time steps over a discretization
|
|
|
|
|
|
|
|
mesh which maintains a constant topology)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- We added a test program to read and solve sparse matrices from files in
|
|
|
|
|
|
|
|
Matrix-Market format (for details see http://math.nist.gov/MatrixMarket/)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TODO:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. Extend the C/F77 interface for character data (some Fortran
|
|
|
|
|
|
|
|
compilers don't just pass a pointer and a hidden length!)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. Provide more general factorizations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|