GitLab

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

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 !

These files can be regenerated with autogen.sh and should not be under
version control.

People having trouble generating them should pick a released tar-ball
which includes them. With sufficiently recent autoconf/automake/libtool,
it should however be easy to successfully run autogen.sh.

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

It contains preprocessor directives which produce warnings or errors
otherwise.

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

As obvious from the previous commits, this release of ELPA
introduces a (optional) QR-decomposition for real valued
matrices. This option can be used at run-time by either setting
an environment variable, or by calling the ELPA-2 solver for
real matrices with an additional flag.

Thus the ABI changed, w.r.t. previous versions.

Furthermore, the build process of ELPA has been made more
consistent. All optimization flags (especially O1, O2 etc.)
have to be set at build time by the user via the CFLAGS, FCFLAGS,
and CXXFLAGS variables. The configure script does not set
automatically the "O-Flags" anymore.

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

Some users where "clever" enough to supply a library in LDFLAGS/LIBS
thath contained omp_get_num_threads, therefore tricking configure into
thinking that we do not need any flags to enable OpenMP.

Now the Fortran test only works if "use omp_lib" and "!$" OpenMP
conditional compilation work.

Also, if no valid OpenMP flag could be detected configure silently
continued. I changed this to an explicit error.

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

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"

These programs have not been updated correctly

Train fdep to recognize

  module procedure ...

lines. Also, previoulsy an fdep internal error aborted make, however the
partially generated dependency file stayed and was used in that form on
a subsequent make call.

It was decided that the version number shall be all of 2014.06.001, that
is including the release version.

Sadly, pkg-config is not too flexible with different versions of
libraries, therefore the pkg-config file will have the full version
number including the release. This might be a bit cumbersome for
dependent projects.

It was decided that the library file shall be called

  libelpa.so.*

without an explicit version string. Version information will be encoded
by using the -version-info parameter of libtool, resulting in an actual
filename as defined by your flavor of Unix.

The file LIBRARY_INTERFACE documents the changes, the current interface
has number 1 and is binary incompatible with the previous version 0.

Conflicts happened only on the print statements with the supported MPI
thread level error message

Small helper module for better error diagnostics