GitLab

Similiar to commits 2998fac3 and 9710bf08 split elpa1.F90 and elpa2.F90
to make merge easier

"Merging" the NVIDIA code by hand , introduced errors.

complex cases

Create automatically two independent routines for real and complex
valued matrices

This commit is not ABI compatible

This commit is not ABI compatible, since it changes the interfaces
of some routines

Also, introduce type checking for transpose and reduce_add routines

Andreas Gloess informed us about a memory leak in ELPA, which was
introduced in version 2013.11.008.

This memory leak is removed now again.

Note, that older versions of ELPA will not be fixed right now.

1. The dimensions of an array have been wrong in cuda calls.
2. Start to get rid of "assumed-size" arrays in the real case
   They are a nightmare to debug and easily lead to a conceptional
   error as in 1.

   Furthermore, the compiler can generally optimize code better if
   "assumed-shape" arrays are used, since more information is available
   at compile time

In the test programms "MPI_ABORT" has been used incorrectly.

The blocksize should be intent(in) and not intent(inout), since
it should not be changed by solve_evlp_real_2stage

If the user chooeses parameters for the QR-decomposition which are
not allowed an error has been produced. This error is caught now,
and the library aborts with a message

It is now possible to switch on more debug messages via
the environment variable "ELPA_DEBUG_MESSAGES=yes"

Error in configure test program fixed

If the QR-decomposition is used wrongly (matrix size is not a
multiple of block size) the the execution will abort, in
order to prevent the wrong results, discussed in a previous commit

Debug messages are now available by setting the environment variable
"ELPA_DEBUG_MESSAGES" to "yes".

We found a bug in the QR-decomposition, which appears for
some matrix sizes and produces wrong results!

If the QR decomposition is switched on, an appropiate warning
is shown.

This bug is still under investigation

- cleanup of the file
- add more  (optional) timing information

The qr decomposition is now available as a runtime choice.
Some testing has still to be done

At build time it can be specified that the ELPA test
programs give more detailed timing information, which
is usefull for performace measurements

Build servers recommend against calling "abort" functions in a
library. Thus, from now on, ELPA  returns a success flag, which
is a change of ABI!

In order to force the user to honour this, the ELPA drivers
are converted to functions, which implies an adaptation and
rebuild of the user code. The driver functions return a
logical "success", which, if it is false, indicates an
error within the library.

It is advised to check catch and check this
return value in the user code, which calls ELPA.