GitLab

Recent GCC complain that an assignment involving a transfer statement
might potentially overflow the destination buffer. This prevented a
build on the SuSE build server.

Replaced this with a proper C string pointer.

Error message there:

 ../src/elpa_driver/legacy_interface/./elpa_driver_c_interface_template.X90:117:0:

        methodFortran(1:charCount) = transfer(method(1:charCount), methodFortran)

 Warning: '__builtin_memset': writing between 1 and 2147483640 bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]

 [...]

 I: Statement might potentially overflow a destination buffer, where a size larger
     than the actual buffer was specified
 E: elpa destbufferoverflow Warning: '__builtin_memset'

There was an error in the strip_width calculation leading to wrong
results for certain values of 'nev'. This is still not properly
investigated, should be checked again.

Exchange _mm512_load_pd()/_mm512_load_ps() of stack variables with
_mm512_set_pd, as the stack variables might not have proper alignment!

Most of the test programs for the new interface were all essentially
copy&pasted from test.F90, now all of those directly use test.F90 with
appropriate preprocessor flags

- Remove all use of ELPA internal modules, the test programs now
  only use the public ELPA API. This is now enforced, by hiding the
  private modules

- Prefix all test internal modules with "test_" to make it really
  clear that these modules are not to be used by users.

whether or not a step is actually computed is decided with logicals
(default all 3 steps are computed). This makes the implementation
of "solve_tridi" and "eigenvalues_only" a bit cleaner in the future

These can be used internally by

  call self%set_private(name, value)

   or

  call self%get_private(name, value)

but are not valid for the self%set()/get() routines, i.e. are not
visible to users of ELPA.

The public "solve" method has been renamed "eigenvectors" since it
computes the eigenvalues and (at least parts of) the eigenvectors

Another routine "eigenvalues" will just compute the eigenvalues