1. 22 Dec, 2015 1 commit
  2. 16 Jun, 2015 1 commit
  3. 26 May, 2015 1 commit
  4. 21 May, 2015 1 commit
  5. 19 May, 2015 1 commit
  6. 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
  7. 28 Apr, 2015 1 commit
  8. 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
  9. 24 Mar, 2015 1 commit
  10. 23 Mar, 2015 2 commits
  11. 19 Mar, 2015 1 commit
  12. 18 Mar, 2015 1 commit
  13. 11 Mar, 2015 2 commits
  14. 11 Feb, 2015 1 commit
  15. 02 Feb, 2015 1 commit
    • Andreas Marek's avatar
      Release version of ELPA_2015.02 · 9aa39397
      Andreas Marek authored
      As obvious from the previous commits, this release of ELPA
      introduces a (optional) QR-decomposition for real valued
      matrices. This option can be used at run-time by either setting
      an environment variable, or by calling the ELPA-2 solver for
      real matrices with an additional flag.
      
      Thus the ABI changed, w.r.t. previous versions.
      
      Furthermore, the build process of ELPA has been made more
      consistent. All optimization flags (especially O1, O2 etc.)
      have to be set at build time by the user via the CFLAGS, FCFLAGS,
      and CXXFLAGS variables. The configure script does not set
      automatically the "O-Flags" anymore.
      9aa39397
  16. 30 Jan, 2015 1 commit
    • Lorenz Huedepohl's avatar
      Improve OpenMP detection in configure.ac · 254bd8ef
      Lorenz Huedepohl authored
      Some users where "clever" enough to supply a library in LDFLAGS/LIBS
      thath contained omp_get_num_threads, therefore tricking configure into
      thinking that we do not need any flags to enable OpenMP.
      
      Now the Fortran test only works if "use omp_lib" and "!$" OpenMP
      conditional compilation work.
      
      Also, if no valid OpenMP flag could be detected configure silently
      continued. I changed this to an explicit error.
      254bd8ef
  17. 29 Jan, 2015 1 commit
  18. 28 Jan, 2015 1 commit
  19. 27 Jan, 2015 1 commit
  20. 25 Aug, 2014 2 commits
    • Andreas Marek's avatar
      ELPA 2014.06.004 Optional usage of detailed timings · ae473b44
      Andreas Marek authored
      At build time it can be specified that the ELPA test
      programs give more detailed timing information, which
      is usefull for performace measurements
      ae473b44
    • Andreas Marek's avatar
      ELPA 2014.06.003: Allow redirect of MPI task output · 7ddffdbd
      Andreas Marek authored
      If specified in the configure step, the test programs
      redirect their stdout and stderr output of each MPI
      task in a seperate file, which will be stored in a
      subdirectory "mpi_stdout".
      
      This will only be done if the environment variable
      "REDIRECT_ELPA_TEST_OUTPUT" is set to "true"
      7ddffdbd
  21. 08 Aug, 2014 1 commit
  22. 02 Jul, 2014 2 commits
    • Lorenz Huedepohl's avatar
      Final(?) version number scheme change · 7ab88e83
      Lorenz Huedepohl authored
      It was decided that the version number shall be all of 2014.06.001, that
      is including the release version.
      
      Sadly, pkg-config is not too flexible with different versions of
      libraries, therefore the pkg-config file will have the full version
      number including the release. This might be a bit cumbersome for
      dependent projects.
      7ab88e83
    • Lorenz Huedepohl's avatar
      Fix libtool library version and naming · 15537712
      Lorenz Huedepohl authored
      It was decided that the library file shall be called
      
        libelpa.so.*
      
      without an explicit version string. Version information will be encoded
      by using the -version-info parameter of libtool, resulting in an actual
      filename as defined by your flavor of Unix.
      
      The file LIBRARY_INTERFACE documents the changes, the current interface
      has number 1 and is binary incompatible with the previous version 0.
      15537712
  23. 01 Jul, 2014 3 commits
  24. 27 Jun, 2014 2 commits
  25. 25 Jun, 2014 2 commits
  26. 16 Jun, 2014 1 commit
  27. 13 Jun, 2014 1 commit
  28. 12 Jun, 2014 1 commit