Apparently in some compiler/MPI combinations (gcc with impi 5.1.3) the
identifier 'mpi_status' is defined and exporeted in their MPI fortran
module and it is thus not allowed to name one of your local variables
also 'mpi_status'.

The confusing error message I got was

  ../src/elpa2_compute.F90:5780:37:

                  call mpi_wait(ireq_hv,mpi_status,mpierr)
                                       1
  Error: Invalid procedure argument at (1)

even though everything seemed to be defined correctly

The subroutine solve_tridi has NOT been shifted from the private
module "elpa1_compute" to the public module elpa1_auxilliary.

Instead, a wrapper function solve_tride has been introduced, which
calls (via Fortran module association) the private function.

This does what it is supposed to do, but should be cleaned up at
some time. Public functions (interfaces) should be implemented in
a public module

These functions were made private with ELPA releases 2016.05.001
and 2016.05.002, but they should be public

Remove all references to private functions and symbols from the public
Fortran modules. Install also only the public modules

The QR decomposition test program can now called with parameters for
matrix size, nev, and block size.
This closses issue #20

- Do not leak "ik", "rk", ..., parameters to use namespace
- Change required ELPA version on configure.ac of test_project

Apparently with "-check all" some versions of the Intel compiler
complain about the use of

  C_SIZEOF(a(1,1,1))

and similar, when a is not already allocated.

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

It turned out that if a CPU supports SSE the already existing
test for SSE assembly instructions always passes.
However, the compilation of gcc SSE intrinic instructions might
nevertheless fail if gcc is not called with one of the options
"-msse3", "-msse4" , "-msse4.1", "-msse4.2", "-mavx", or "-mavx2"!

Obviously gcc does still not consider SSE as a standard on X86_64
Intel CPUs.

An additional configure test has been introduced, which test for
gcc intrinsic sse instructions. If this test fails, the corresponding
kernels are switched off.

The C++ kernels can be written as C kernels, which simplifies the build
procedure

In order to increase type safty all ELPA2 kernels provide now
an interface. The interfaces for the C/C++ kernels are automatically
generated during the configure step

The utility binary printed the available kernels to stderr.
This is changed. The ELPA library itself still does all prints
on stderr

For the Intel compiler, this was assured with the pragma

  !DEC$ ATTRIBUTES ALIGN: 64:: a

however, other compilers such as gcc of course did not honour this,
which could result in SIGSEGVs in case the variable was not aligned to
32 bytes (by chance!).

This fixes issue #11, thanks to Nico Holmberg for reporting this.

The SSE kernels with blocking of 2,4,6 (real case) and 1,2 (complex)
case are now available by default

Thus the following changes have been done
- introduce new macros in configure.ac and Makefile.am
- renmae the AVX kernels in AVX_AVX2 (they also support AVX2)
- introduce new files with SSE kernel
- introduce new kernel parameters !
- make the SSE kernels callable

The results are identical with previous kernels

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

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