1. 12 Feb, 2017 1 commit
  2. 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
  3. 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
  4. 23 Nov, 2016 1 commit
  5. 11 Nov, 2016 1 commit
  6. 09 Nov, 2016 1 commit
  7. 27 Oct, 2016 1 commit
  8. 26 Oct, 2016 1 commit
  9. 25 Oct, 2016 1 commit
  10. 18 Oct, 2016 1 commit
  11. 12 Oct, 2016 1 commit
  12. 29 Sep, 2016 1 commit
  13. 28 Sep, 2016 2 commits
  14. 23 Sep, 2016 1 commit
  15. 02 Sep, 2016 2 commits
  16. 22 Aug, 2016 1 commit
    • 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
  17. 17 Aug, 2016 1 commit
  18. 16 Aug, 2016 1 commit
  19. 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
  20. 07 Jul, 2016 1 commit
  21. 04 Jul, 2016 2 commits
  22. 22 Jun, 2016 1 commit
  23. 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
  24. 14 Jun, 2016 2 commits
  25. 30 May, 2016 7 commits
  26. 25 May, 2016 2 commits
  27. 24 May, 2016 1 commit