1. 18 Nov, 2017 2 commits
  2. 13 Nov, 2017 1 commit
  3. 01 Nov, 2017 1 commit
  4. 31 Aug, 2017 1 commit
  5. 30 Aug, 2017 1 commit
  6. 22 Aug, 2017 1 commit
  7. 10 Aug, 2017 1 commit
  8. 05 Aug, 2017 1 commit
  9. 14 Jul, 2017 1 commit
  10. 07 Jul, 2017 1 commit
  11. 02 Jul, 2017 1 commit
  12. 30 Jun, 2017 1 commit
  13. 02 Jun, 2017 1 commit
  14. 01 Jun, 2017 1 commit
    • Lorenz Huedepohl's avatar
      A bit of cleanup of the test programs · 958032ef
      Lorenz Huedepohl authored
      - 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.
      958032ef
  15. 24 May, 2017 2 commits
  16. 18 May, 2017 1 commit
  17. 17 May, 2017 1 commit
  18. 16 May, 2017 4 commits
  19. 15 May, 2017 1 commit
  20. 27 Apr, 2017 2 commits
  21. 26 Apr, 2017 1 commit
    • Lorenz Huedepohl's avatar
      Workaround for PGI compiler · f4aece79
      Lorenz Huedepohl authored
      PGI's compiler wants
      
        -module
      
      as the flag to specify the module output directory. Sadly, this is also
      a libtool argument, resulting in much sorrow.
      
      Thus, we have to escape -module by prefixing it with -Xcompiler. Sadly
      libtool is not used everywhere by automake, thus we have to remove it
      again in those cases were it would be passed to the compiler and cause
      sorrow there.
      
      Sad story. But with a happy ending?
      f4aece79
  22. 24 Apr, 2017 1 commit
  23. 21 Apr, 2017 2 commits
  24. 18 Apr, 2017 1 commit
  25. 06 Apr, 2017 1 commit
  26. 16 Mar, 2017 1 commit
  27. 10 Mar, 2017 1 commit
  28. 13 Feb, 2017 2 commits
    • Lorenz Huedepohl's avatar
      Work around Intel compiler oddities · 7e1dea02
      Lorenz Huedepohl authored
      For some reason, and only in certain cases, the built-in
      preprocessor of ifort cannot handle constructs such as
      
        #define FOO bar
      
        print *, "foo&
        &FOO&
        &baz"
      
      or more specifically
      
        #define DATATYPE double
      
        print *, some_&
        &DATATYPE&
        &_routine
      
      which, however, are quite handy. GCC seems to handle those as
      expected.
      7e1dea02
    • Andreas Marek's avatar
      Make blocking in trans_ev_band_to_full default · f3ce5bd3
      Andreas Marek authored
      This gives a speed-up of up to a factor 2 in the complex version
      f3ce5bd3
  29. 12 Feb, 2017 3 commits
  30. 08 Feb, 2017 1 commit
    • Andreas Marek's avatar
      Introduce configure flag for CUDA GPU compute capability · 4126e87e
      Andreas Marek authored
      Now the CUDA compute capability is not hard-coded anymore.
      Setting
      
      --with-gpu-compute-capability=value
      
      set the nvcc compiler option "-arch value".
      
      A simple sanity checking is done to ensure that "value" is not
      completely unreasonable
      4126e87e