In case of SSE/AVX/AVX2 it could happen that more than one kernel
(since some depend on other kernels, e.g. block 6 on block 4 and
block 2) were called

files

The test programs include the same template now, the
printed messages are thus unified

The configure flag "--enable-shared-memory-only" triggers a build
of ELPA without MPI support:

- all MPI calls are skipped (or overloaded)
- all calls to scalapack functions are replaced by the corresponding
  lapack calls
- all calls to blacs are skipped

Using ELPA without MPI gives the same results as using ELPA with 1 MPI
task!

This version is not yet optimized for performance, here and there some
unecessary copies are done.

Ths version is intended for users, who do not have MPI in their
application but still would like to use ELPA on one compute node

The Fortran variable declerations "variable type*[4,8,16]" is non
Fortran standard. It might cause problem in the future.
Furthermore, the usage of Fortran and C togehther is more clean
if variables are defined according to C variable types.

This is done, now for all the test programs

This commit does not change the interfaces defined in ELPA_2015.11.001 !
All functionality is available via the interface names and definitions
as in ELPA_2015.11.001

But some new interfaces have been added, in order to unfiy the
references from C and Fortran codes:

- The procedures to create the ELPA (row/column) communicators are now
  available from C _and_ Fortran with the name "get_elpa_communicators".
  The old Fortran name "get_elpa_row_col_comms" and the old C name
  "elpa_get_communicators" are from now on deprecated but still available

- The 1-stage solver routines are available from C _and_ Fortran via
  the names "solve_evp_real_1stage" and "solve_evp_complex_1stage".
  The old Fortran names "solve_evp_real" and "solve_evp_complex" are
  from now on deprecated but still functional.

All documentation (man pages, doxygen, and example test programs) have
been changed accordingly.

This commit implies a change in the API versioning number, but no
changes to codes calling ELPA (if they have been already updated to the
API of ELPA_2015.11.001)

- the contact email is now: elpa-library@mpcdf.mpg.de
- the official website is now hosted at http://elpa.mpcdf.mpg.de

The Rechenzentrum Garching (RZG) has been renamed into
the Max Planck Computing and Data Facility (MPCDF).

This is reflected now in the adapted headers.

In the near future, all references to the ELPA webside and
the ELPA email will also be adapted.

The examples, how to invoke ELPA from a c program have been updated.
There are now examples for ELPA1 and ELPA2 both real and complex case.
The test cases are still with less functionality than their Fortran
counter parts, they are just ment as a "proof-of-concept".

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

Also, introduce type checking for transpose and reduce_add routines

C interfaces are now available and definied in the header
elpa.h

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

The procedure "get_elpa_row_col_comms" is now a function instead
a subroutine and returns an error code.

This should have been done previously when all the other ELPA
function have been updated to return an error code.

This requires an ABI change in the next ELPA release !

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".

For an MPI library that does not support MPI_THREAD_MULTIPLE the tests
now report "SKIP" instead of "FAIL".

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

If specified in the configure step, the test programs
redirect their stdout and stderr output of each MPI
task in a seperate file, which will be stored in a
subdirectory "mpi_stdout".

This will only be done if the environment variable
"REDIRECT_ELPA_TEST_OUTPUT" is set to "true"

Small helper module for better error diagnostics

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.

Now it is possible
- to choose the kernel (real and complex independently) at run-time
  via environment variables, or
- to specify the kernel (real and complex independently) at runtime
  via specifing the kernel in the call to ELPA

This has a few implications
1) The ELPA 2014.06 release has a change in the API and is thus not
   binary compatible with previous versions
2) if no kernels are specified, a default kernel is choosen
3) if a wrong kernel is specified, a default kernel is choosen

For sake of simplicity it is still possible to build ELPA with
support for only one kernel, as in previous versions. However, it is
still not binary compatible to previous versions

If the ELPA library is compiled with OpenMP, the tests check
whether the MPI library provides the neccessary threading level.

There has been the error, that if the required threading level
was not available the test programs aborted, put no explicit
error code was set. This is changed now.

This is the release of the ELPA_development_version_OpenMP
If OpenMP support is not used, this version has the same
functionality as ELPA_2013.08.

If OpenMP support is used, obviously, a hybrid version of ELPA will be
build.

Allthough this is a release, version ELPA_2013.11 is far from complete!
During the next week optimizations of the OpenMP part will be published,
however, the basic functionality is set by this commit

If ELPA is compiled with OpenMP the MPI_INIT_THREAD with
level THREAD_MULIPLE must be called. This is changed in the test
programs

The test examples are a little bit more verbose if OpenMP is
used

This commit introduces OpenMP functionality in the
ELPA_development_version_OpenMP branch.

It contains several bugfixes to the OpenMP functionality in the
branch "ELPA_development_version", the later will soon be deleted
since the new branch is the new reference implementation.

The current branch contains the following features/bugfixes:
- building of the OpenMP version of ELPA via configure and the
  "--with-openmp" flag. The build library contains a "_mt"
  (multi-threaded) in its name.
  The configure procedure should (hopefully) determine for each
  compiler the neccessary OpenMP flags.
  If the "--with-openmp" flag is ommitted exactly the same code
  as in the ELPA 2013.08.001 release is used and build in the
  same way
- The example test cases print which kernels have been used and
  how many OpenMP threads are used at runtime
- correct handling of OpenMP stack arrays: the previous implementation
  caused compiler dependent segmentation faults
- OpenMP capability with all available kernels: the correctness of
  the computations have been checked for all kernels except the
  Bluegene (P/Q) versions

Based on the ELPA 2013.08.001 a development version for ELPA OpenMP
has been created

For debugging purposes the test examples of the ELPA library can
now write the Eigenvectors in an ascii file, e.g
a call of "test_real 4000 1500 16 output" will envoke the test
case for real matrices of the ELPA1 library. A matrix of 4000x4000
values will be created an 1500 EV's will be computet with a 16 blocking.
And the results will be --- due to the output flag --- written to a
text file

This commit releases ELPA version 2013.08

It is identical with the latest commit version 2013.02_BETA, except:

- rename ELPA_2013.02.BETA -> ELPA_2013.08
- update of configure.ac
- remove of src/elpa2.f90_save
- remove of test/Makefile

This version has been tested extensivly, however, there might always
be some bugs.
In case of questions please contact elpa-library@rzg.mpg.de or via
the ELPA forum on http://elpa-lib.fhi-berlin.mpg.de/forum/index.php