1. 15 Feb, 2021 1 commit
  2. 21 Jan, 2021 1 commit
  3. 18 Nov, 2020 1 commit
  4. 17 Nov, 2020 1 commit
  5. 10 Aug, 2020 1 commit
  6. 31 Jul, 2020 2 commits
  7. 03 Apr, 2020 1 commit
  8. 24 Mar, 2020 1 commit
  9. 02 Mar, 2020 1 commit
  10. 28 Feb, 2020 1 commit
  11. 28 Oct, 2019 1 commit
    • Pavel Kus's avatar
      partially addressing issues with the GPU kernel · ec5b3bec
      Pavel Kus authored
      This commit addresses several issues. It essentially forbids the use of
      the GPU kernel, which become obsolete and caused problems. But it
      does not complete remove the related code, nor does it forbid from
      explicitly selecting the GPU kernel. However, if the user does select
      it, the warning will be issued and the GENERIC kernel would be used
      instead. In the more details:
      * Commentin out operations in the GPU kernel, which do not compile with
        CUDA 10.1. This makes the kernel deffinitely not ussable (but it was
        true even before)
      * removing the gpu_tridiag_band option, sincie the tridiag->banded routine
        is actually not ported to GPU at all. This step will thus always be
        run on the CPU
      * removing the gpu_trans_ev_tridi_to_band option, since the GPU version
        of this step cannot run without the GPU kernel and it is not usable.
        This step will thus also be performed on the CPU
      * modifying REAL_GPU_KERNEL_ONLY_WHEN_GPU_IS_ACTIVE and
        COMPLEX_GPU_KERNEL_ONLY_WHEN_GPU_IS_ACTIVE such that the GPU kernel is
        not considered during the autotuning
      
      * TODO however, the GPU kernel can still be enforced by the user. In
        this case, during the calculation, a warning is issued and the kernel
        is switched to the GENERIC one. This should be improved and there
        should not even be the possibility to choose the GPU kernel at the
        begining.
      ec5b3bec
  12. 14 Oct, 2019 1 commit
  13. 26 Jun, 2019 1 commit
  14. 25 Apr, 2019 2 commits
  15. 06 Feb, 2019 1 commit
  16. 23 Jan, 2019 2 commits
    • Lorenz Huedepohl's avatar
      Fix error in elpa_index · fd2bb65c
      Lorenz Huedepohl authored
      lfind() expects a proper comparison function where the order of the
      arguments does not matter. Previously it was assumed that the first
      argument is always a pointer to an unspecific "key" object and the
      second argument a pointer to an array member to compare against.
      
      However, the standard requires the two arguments to be interchangeable
      pointers to array-member like objects.
      
      Surfaced as musl-libc does in fact call it the other way around,
      compared to glibc.
      fd2bb65c
    • Lorenz Huedepohl's avatar
      4be39b35
  17. 11 Dec, 2018 1 commit
  18. 03 Dec, 2018 1 commit
  19. 21 Nov, 2018 1 commit
    • Pavel Kus's avatar
      changed logic of setting mpi communicators · f3144dd9
      Pavel Kus authored
      mpi_comm_parent is allways requred (it was not required before, but
      actually the code internals expected it to be supplied, at least for
      ELPA 2 calculation OR whenever GPU was used)
      f3144dd9
  20. 13 Nov, 2018 2 commits
  21. 07 Nov, 2018 1 commit
  22. 06 Nov, 2018 1 commit
  23. 18 Oct, 2018 1 commit
  24. 27 Sep, 2018 1 commit
  25. 27 Aug, 2018 4 commits
  26. 14 Aug, 2018 3 commits
  27. 13 Aug, 2018 1 commit
  28. 10 Aug, 2018 4 commits