1. 07 Dec, 2015 1 commit
    • Andreas Marek's avatar
      Bugfix in ELPA_2015.11.001, roll back of minor changes · 402629d9
      Andreas Marek authored
      For some matrix/block size combinations the real case of ELPA2
      crashes, e.g:
      
      mpiexec -n 1 ./elpa2_test_real 50 50 32
      
      leads to an error message
       ** On entry to DGEMM parameter number  3 had an illegal value
       and a crash.
      
      This only seems to happen with matrix size smaller than 64*64.
      he code path responsible for this has been identified, but the problem
      tself is not yet solved!
      
      The part of the code, which causes these crashes, has been switched on
      as default by Intel in commit fe63372d. The rest of the commit fe63372d
      seems to be fine, and is performance critical.
      
      As an intermediate step, the responsible code path is switched off again
      as default, this will be changed again once the underlying root cause
      has been solved.
      402629d9
  2. 26 Nov, 2015 1 commit
    • Andreas Marek's avatar
      ELPA_2015.11 release fix · 318ba8e2
      Andreas Marek authored
      The API versioning number was not updated correctly at the release.
      This lead to a wrong soname.
      
      This is fixed now
      318ba8e2
  3. 16 Nov, 2015 4 commits
  4. 13 Nov, 2015 2 commits
  5. 11 Nov, 2015 1 commit
  6. 05 Nov, 2015 5 commits
  7. 04 Nov, 2015 3 commits
  8. 03 Nov, 2015 2 commits
    • Andreas Marek's avatar
      Remove of Makefile.example · d86c8c96
      Andreas Marek authored
      A build without autotools is not officially supported anymore.
      Thus this --- broken since long time --- Makefile.example is removed
      d86c8c96
    • Andreas Marek's avatar
      Update of c test cases · 505004e7
      Andreas Marek authored
      The examples, how to invoke ELPA from a c program have been updated.
      There are now examples for ELPA1 and ELPA2 both real and complex case.
      The test cases are still with less functionality than their Fortran
      counter parts, they are just ment as a "proof-of-concept".
      505004e7
  9. 28 Oct, 2015 1 commit
    • Alexander Heinecke's avatar
      This commit improves ELPA's performance on Intel(R) Xeon(R) E5v2 and E5v3 series CPUs by: · fe63372d
      Alexander Heinecke authored
      - enabling fusing iterations of stage 5 in ELPA2 for every configuration
      - Changed reduction bandwidth in ELPA2 to be at least 64
      - partial OpenMP parallelization of the QR factorization in bandred_real
      - OpenMP parallelization of SYMM
      - OpenMP parallelization of SYR2K in bandred_real
      - OpenMP parallelization for elpa1_reduce_add_vectors and elpa1_transpose_vectors
      - AVX2 support in backtransformation elpa2_kernels (FMA3 instructions introduced with Haswell microarchitecture)
      fe63372d
  10. 24 Aug, 2015 1 commit
  11. 16 Jun, 2015 3 commits
  12. 28 May, 2015 3 commits
  13. 26 May, 2015 3 commits
  14. 19 May, 2015 3 commits
  15. 29 Apr, 2015 2 commits
  16. 28 Apr, 2015 4 commits
  17. 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