1. 30 Jun, 2017 5 commits
  2. 29 Jun, 2017 4 commits
  3. 28 Jun, 2017 7 commits
  4. 27 Jun, 2017 1 commit
  5. 26 Jun, 2017 1 commit
  6. 14 Jun, 2017 5 commits
  7. 13 Jun, 2017 5 commits
  8. 12 Jun, 2017 3 commits
    • Lorenz Huedepohl's avatar
    • Lorenz Huedepohl's avatar
      Limit file name length to 250 characters · ac90d643
      Lorenz Huedepohl authored
      Otherwise we stumble upon file system limits when 'manual_cpp' has to be
      used. This whole situation with the 'manual_cpp' is very unsatisfying...
    • Lorenz Huedepohl's avatar
      Had to move some functions to the public namespace · 38335f50
      Lorenz Huedepohl authored
      The PGI compiler (of course) complained about a missing module
      (elpa_generated_fortran_interfaces.mod) when compiling the test
      It is true (in a way) that some part of this module is indeed necessary,
      as the public-facing function signatures have arguments that are
      referring to those three functions in their type:
        elpa_int_value_to_string_c(name, value, string)
        elpa_int_value_to_strlen_c(name, value)
      Thus, for these three we create another header prefix,
      for Fortran definitions that should be public. Those are included in
  9. 11 Jun, 2017 1 commit
  10. 10 Jun, 2017 1 commit
  11. 09 Jun, 2017 5 commits
    • Andreas Marek's avatar
    • Andreas Marek's avatar
    • Lorenz Huedepohl's avatar
      Prevent some more warnings about uninitialized uses · 6688e40c
      Lorenz Huedepohl authored
      It is not quite clear to me why GCC complains here when
      WANT_SINGLE_PRECISION_REAL is not defined, as the variables are then not
      used _at all_.
      Nonetheless, this again prevents build on the SuSE OBS, so fix it to
      make the compiler happy
    • Lorenz Huedepohl's avatar
    • Lorenz Huedepohl's avatar
      Prevent compiler error due to uninitialized value · 333572d9
      Lorenz Huedepohl authored
      Another blocker for the SuSE build server: Even though the variable is
      later not actually used by the function, a recent GCC complains about
      the use of an uninitialized value for that variable.
      This prevents build on the OBS, as they use compiliation flags that
      detect such behaviour.
      Error message there:
       ../test/C/driver/legacy_interface/legacy_real_driver_c_version.c:193:12: warning: 'THIS_REAL_ELPA_KERNEL_API' is used uninitialized in this function [-Wuninitialized]
           success = elpa_solve_evp_real_double(na, nev, a, na_rows, ev, z, na_rows, nblk, na_cols, mpi_comm_rows, mpi_comm_cols, my_mpi_comm_world, THIS_REAL_ELPA_KERNEL_API, useQr, useGPU,
       I: Program is using uninitialized variables.
          Note the difference between "is used" and "may be used"
       W: elpa uninitialized-variable ../test/C/driver/legacy_interface/legacy_real_driver_c_version.c:193
  12. 08 Jun, 2017 1 commit
  13. 07 Jun, 2017 1 commit
    • Lorenz Huedepohl's avatar
      Refactor unsafe string conversion with C pointers · 0d444556
      Lorenz Huedepohl authored
      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:
              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'