1. 21 Apr, 2017 2 commits
  2. 18 Apr, 2017 1 commit
  3. 06 Apr, 2017 1 commit
  4. 16 Mar, 2017 1 commit
  5. 10 Mar, 2017 1 commit
  6. 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
  7. 12 Feb, 2017 3 commits
  8. 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
  9. 25 Nov, 2016 1 commit
    • Andreas Marek's avatar
      Update of ELPA version number to 2016.11.001.pre · a1da48c1
      Andreas Marek authored
      - the version number has been updated
      - a warning that this is a pre-release has been added to the configure
        script
      - the changelog has been updated
      - the test_project versioning is consistent with the ELPA versioning
      a1da48c1
  10. 23 Nov, 2016 1 commit
  11. 11 Nov, 2016 1 commit
  12. 09 Nov, 2016 1 commit
  13. 27 Oct, 2016 1 commit
  14. 26 Oct, 2016 1 commit
  15. 25 Oct, 2016 1 commit
  16. 18 Oct, 2016 1 commit
  17. 12 Oct, 2016 1 commit
  18. 29 Sep, 2016 1 commit
  19. 28 Sep, 2016 2 commits
  20. 23 Sep, 2016 1 commit
  21. 02 Sep, 2016 3 commits
  22. 22 Aug, 2016 2 commits
    • Andreas Marek's avatar
      Better control of AVX kernels · d4ab9550
      Andreas Marek authored
      Sometimes it might be desirable that only one of the specifc AVX
      kernels (AVX, AVX2, and in the future AVX512) are build, even though the processor
      supports all (or several) of these instructions.
      
      The flag --disable-[avx | avx2 | avx512] allows to define which kernels
      should NOT be build. The default is: what can be build will be build
      d4ab9550
    • Andreas Marek's avatar
      Better control of AVX kernels · 5a1efab3
      Andreas Marek authored
      Sometimes it might be desirable that only one of the specifc AVX
      kernels (AVX, AVX2, AVX512) are build, even though the processor
      supports all (or several) of these instructions.
      
      The flag --disable-[avx | avx2 | avx512] allows to define which kernels
      should NOT be build. The default is: what can be build will be build
      5a1efab3
  23. 17 Aug, 2016 1 commit
  24. 16 Aug, 2016 1 commit
  25. 08 Jul, 2016 2 commits
    • Lorenz Huedepohl's avatar
      Fix actual reason for linker problems · 2121b2e5
      Lorenz Huedepohl authored
      The actual reason for the linker problems was that the Fortran libraries
      where listed before the object files, by modifying the _LINK automake
      variables. The proper way to do is of course to add the necessary
      libraries after the object files by appending them to the _LDADD
      variables.
      
      As the MPI module was not responsible for the linker problems it is now
      used by default, unless explicitly switched off with
      
        --disable-mpi-module
      
      Also, the C test programs that had these linker errors where previously
      not compiled in the OpenMP case, for no obvious reason. Now they are
      also included there.
      2121b2e5
    • Lorenz Huedepohl's avatar
      Make 'use mpi' usage optional · 7a54b546
      Lorenz Huedepohl authored
      For some strange reason this causes linker errors on _some_
      openSUSE_Tumbleweed installations..
      7a54b546
  26. 07 Jul, 2016 1 commit
  27. 04 Jul, 2016 2 commits
  28. 22 Jun, 2016 1 commit
  29. 15 Jun, 2016 2 commits
    • Lorenz Huedepohl's avatar
      Cleanup of configure arguments · 0da56d61
      Lorenz Huedepohl authored
      It is now
      
        --enable-timing
        --enable-redirect
        --with-papi
      
      instead of the more confusing
      
        --with-ftimings
        --with-redirect
        --disable-papi
      
      For once, the --with versions of timing and redirect could not cope with
      --with-timing=no, --with-redirect=no (this was interpreted like =yes).
      Also, --with switches are supposed to be for optional dependencies on
      other software, not for configuring optional parts of the software
      itself.
      0da56d61
    • Andreas Marek's avatar
      e451b897