1. 15 Mar, 2019 1 commit
  2. 05 Mar, 2019 4 commits
  3. 04 Mar, 2019 1 commit
  4. 03 Mar, 2019 1 commit
  5. 02 Mar, 2019 1 commit
  6. 01 Mar, 2019 3 commits
  7. 27 Feb, 2019 3 commits
  8. 26 Feb, 2019 1 commit
  9. 25 Feb, 2019 1 commit
  10. 24 Feb, 2019 1 commit
  11. 23 Feb, 2019 1 commit
  12. 22 Feb, 2019 5 commits
  13. 20 Feb, 2019 2 commits
  14. 19 Feb, 2019 1 commit
  15. 18 Feb, 2019 1 commit
  16. 15 Feb, 2019 2 commits
  17. 11 Feb, 2019 1 commit
  18. 07 Feb, 2019 2 commits
  19. 06 Feb, 2019 2 commits
  20. 05 Feb, 2019 1 commit
  21. 23 Jan, 2019 2 commits
    • Lorenz Hüdepohl's avatar
      Fix error in elpa_index · fd2bb65c
      Lorenz Hüdepohl 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 Hüdepohl's avatar
      4be39b35
  22. 09 Jan, 2019 1 commit
  23. 06 Jan, 2019 1 commit
  24. 04 Jan, 2019 1 commit
    • Andreas Marek's avatar
      Fix problem in elpa2_print_kernels with GPU kernel · f3a1d0f2
      Andreas Marek authored
      The GPU kernel can only be set, if e%set("use_gpu",1) has been set
      before and GPU usage was thus requested.
      
      In the elpa2_print_kernels, this was not reflected, and the GPU kernels
      were checked via can_set method without activating GPU usage
      => GPU kernels were always reported as non exisitent
      f3a1d0f2