1. 22 Dec, 2015 2 commits
  2. 17 Jun, 2015 2 commits
  3. 16 Jun, 2015 4 commits
  4. 02 Jun, 2015 1 commit
  5. 01 Jun, 2015 3 commits
  6. 28 May, 2015 3 commits
  7. 26 May, 2015 5 commits
  8. 21 May, 2015 4 commits
  9. 19 May, 2015 3 commits
  10. 29 Apr, 2015 5 commits
    • Andreas Marek's avatar
      Cleanup of configure.ac · 701a7cff
      Andreas Marek authored
      Remove variables which are not needed (anymore)
      701a7cff
    • Andreas Marek's avatar
      configure.ac: move ELPA specific macros into ./m4 · 93c19c5e
      Andreas Marek authored
      The macros which define the functionality to test
      for
       - a specific real/complex kernel (not all available kernels)
      
      are now defined in files in the m4 directory
      93c19c5e
    • Andreas Marek's avatar
      Cleanup of configure.ac · 18c83c76
      Andreas Marek authored
      Remove variables which are not needed (anymore)
      18c83c76
    • Andreas Marek's avatar
      configure.ac: move ELPA specific macros into ./m4 · c788ec6b
      Andreas Marek authored
      The macros which define the functionality to test
      for
       - GPU support only (no CPU based kernels)
       - a specific real/complex kernel (not all available kernels)
      
      are now defined in files in the m4 directory
      c788ec6b
    • Andreas Marek's avatar
      configure.ac: treat GPU kernel as other kernels · 0a27d7c8
      Andreas Marek authored
      Configure treats the GPU kernels now as any other kernel, i. e.
      if GPU support is enabled (and it is possible to build it) then
      it will be build in ADDITION to all other possible kernels for
      the desired hardware.
      
      Also, it is possbile to configure the build process for
      the GPU version ONLY (as it was already possible to trigger the
      build for only ONE specific real/complex kernel).
      
      Note: The sources at the moment CANNOT handle this, i.e. if
      GPU support is configured, the GPU only code path is compiled.
      This will be changed in the near future.
      0a27d7c8
  11. 28 Apr, 2015 7 commits
  12. 27 Apr, 2015 1 commit
    • Lorenz Huedepohl's avatar
      Handle different OpenMP flags for Fortran and C · ba9a188f
      Lorenz Huedepohl authored
      There was an inconsistency when the OpenMP flag was different for the
      Fortran and C compiler (e.g. -openmp for ifort and -fopenmp for gcc).
      
      This led to strange errors when linking the example program with the C
      main() routine when using Intel Fortran, Intel MPI, and GCC together, a
      typical error message was
      
        /usr/bin/ld: MPIR_Thread: TLS definition in [...]/intel64/lib/libmpi_dbg_mt.so section .tbss mismatches non-TLS definition in [...]/intel64/lib/libmpi_dbg.so section .bss
        [...]/intel64/lib/libmpi_dbg_mt.so: could not read symbols: Bad value
      
      The reason seems to be that the various MPI wrapper shell scripts
      (mpicc, mpiifort) need the correct OpenMP option to select the
      thread-safe Intel MPI debug library. Previously, always OPENMP_FCFLAGS
      was appended to LDFLAGS, which did not trigger this when linking a C
      main program with mpicc.
      ba9a188f