This reverts commit 64ec6ec2.

- The SSE part will be available in different files.
- Specify whether AVX or AVX2 was used to build

library

It the configure option "--enable-single-precision" is specified,
ELPA will also be build for single precision usage. The double precision
and single precision will be available at the same time with names
"solve_evp_real_1stage_double" or "solve_evp_real_1stage_single" and
so on...

This change immplied some major refactoring of the ELPA code:
1.) functions/procedures had to be renamed with suffix "_double"

2.) If necessary the same functions have to be available with suffix
"_single"

3.) Variable kind definitions have to be consistent with the
intented use

To avoid uneccessary code duplication this is done (most of the time)
with preprocessor string substitution.

The documentation has been updated.

NOT SUPPORTED are at the moment:

- single precision usage of ELPA2 with kernels, others than "generic"
  and "generic_simple"

- single precision usage of GPU

All variables (real, integer, complex) are now declecared with the
appropiate kind statement. The definition of the kind types is done
in src/mod_precision.f90

To ensure interoperability with C, the kind types are decleared via
iso_c_binding to C variables

- 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 user functions of ELPA are now documented with doxygen tags.
At the moment the interface of ELPA 2015.11.001 is decribed.

The documentation has step by step to be implemented for all functions
and test programms.

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

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

The configure.ac of ELPA_2013.11 is cleaned up a bit
Also, ELPA_2013.11 is copied to ELPA_2014.06 in order to have
the base for the next ELPA release

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

On behalf of the Elpa Consortium and due to a remark of
Volker Blum the license model of ELPA is "corrected"

- each file now contains the appropiate header
- the files in the subdirectory "COPYING" are now
  in accordance with LGPL v. 3, the license we choose
  to use

created 2013.02 release

Added OpenMP enhancements to elpa2.f90
Removed MPI-2 dependencies, ELPA should now work with pure MPI-1
Added x86_64 optimized assembler version of the kernels.
Added a straight forward and simple version of the kernels.
Added a description of the kernels.