1. 29 Jan, 2015 1 commit
  2. 28 Jan, 2015 1 commit
  3. 27 Jan, 2015 1 commit
  4. 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
  5. 08 Aug, 2014 1 commit
  6. 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
  7. 01 Jul, 2014 3 commits
  8. 27 Jun, 2014 2 commits
  9. 25 Jun, 2014 2 commits
  10. 16 Jun, 2014 1 commit
  11. 13 Jun, 2014 1 commit
  12. 12 Jun, 2014 1 commit
  13. 11 Jun, 2014 1 commit
  14. 10 Jun, 2014 1 commit
    • Lorenz Huedepohl's avatar
      Make ELPA ready for packaging as RPM · 7ea5c43a
      Lorenz Huedepohl authored
      This includes a number of changes:
      
      - ScaLAPACK2 on from the openSUSE:science repository is now correctly
        auto-detected. As ScaLAPACK2 already includes BLACS, an additional
        BLACS library must not be linked!
      
      - The resulting library is now called elpa-2014.06.000.so, as was
        probably originally intended anyway
      
      - The pkg-config file was renamed to elpa-2014.06.000.pc and filled with
        correct values. With this, a package using ELPA can easily get the
        necessary compilation and library flags.
      
      In this commit, only the "precious" files (Makefile.am, configure.ac,
      etc.) are included, to make clear what has been changed by hand.
      
      In the subsequent commit also all autoconf generated files will follow.
      7ea5c43a
  15. 08 Jun, 2014 1 commit
    • Lorenz Huedepohl's avatar
      Disable maintainer mode for automake · 6dea7b4a
      Lorenz Huedepohl authored
      Without this, automake tries to be smart and rebuilt the autoconf
      generated files such as configure, aclocal.m4, etc., in case the
      timestamps of files such as configure.ac are newer.
      
      This only makes trouble for end users with out-of-date autoconf versions
      that cannot produce these files.
      6dea7b4a
  16. 06 Jun, 2014 1 commit
  17. 05 Jun, 2014 2 commits
  18. 28 May, 2014 3 commits
  19. 27 May, 2014 3 commits
  20. 26 May, 2014 3 commits
    • Andreas Marek's avatar
      ELPA_2014.06 prepare release · 53f2f2c6
      Andreas Marek authored
      Now it is possible
      - to choose the kernel (real and complex independently) at run-time
        via environment variables, or
      - to specify the kernel (real and complex independently) at runtime
        via specifing the kernel in the call to ELPA
      
      This has a few implications
      1) The ELPA 2014.06 release has a change in the API and is thus not
         binary compatible with previous versions
      2) if no kernels are specified, a default kernel is choosen
      3) if a wrong kernel is specified, a default kernel is choosen
      
      For sake of simplicity it is still possible to build ELPA with
      support for only one kernel, as in previous versions. However, it is
      still not binary compatible to previous versions
      53f2f2c6
    • Andreas Marek's avatar
      Prepare 2014.06.000: check for Fortran environment · c090a89f
      Andreas Marek authored
      Configure checks whether the Fortran environment module
      is available. If yes, the library is build such, that all
      messages (from within the library) are printed at the correct
      stderr unit. If not, then the stderr unit is set to unit=6
      c090a89f
    • Andreas Marek's avatar
      Cleanup of configure.ac ELPA_2013.11; Create ELPA_2014.06 · b3d47d1e
      Andreas Marek authored
      The configure.ac of ELPA_2013.11 is cleaned up a bit
      Also, ELPA_2013.11 is copied to ELPA_2014.06 in order to have
      the base for the next ELPA release
      b3d47d1e
  21. 21 Mar, 2014 1 commit
  22. 03 Mar, 2014 1 commit
  23. 27 Feb, 2014 1 commit
    • Andreas Marek's avatar
      ELPA_2013.11.006 bugfix for kernels real blocking 6 and 4 · f0c7cb0d
      Andreas Marek authored
      Due to an error in a preprocessor statement, the results for
      real matrices were wrong if the kernels "avx-real-block6" or
      "avx-real-block4" were chosen. No other kernels are affected.
      
      The test programms always correctly stated that the results for
      these kernels are wrong.
      f0c7cb0d
  24. 26 Feb, 2014 1 commit
    • Andreas Marek's avatar
      ELPA_2013.11.005 Changes in OpenMP detection · c4e3b88c
      Andreas Marek authored
      The Intel Fortran compiler accepts the flag "-fopenmp" for compilation
      with OpenMP. However, the Intel MPI compiler wrapper does not.
      With the Intel compiler, this leads to the fact, that if ELPA is compiled
      with the "-fopenmp" flag a not thread-save version of the Intel MPI
      library is used and the test (with make check) fails.
      
      Intel promised to solve this in the future.
      
      However, for now the problem is solved in the user friendly way that no
      manipulation of the MPI compiler wrappers have to be done:
      
      For detecting the OpenMP compiler flags, instead of the predefined
      macro "AC_OPENMP" of autoconf a modified macro "AX_ELPA_OPENMP"
      is used, which first checks "-openmp" and only then "-fopenmp".
      Thus it is ensured that the Intel compiler (and mpi compiler wrapper)
      does not get confused.
      
      This is invisible for users calling "configure" during the installation
      process.
      c4e3b88c
  25. 24 Feb, 2014 1 commit
  26. 18 Dec, 2013 1 commit
  27. 10 Dec, 2013 1 commit
    • Andreas Marek's avatar
      ELPA 2013.11.003 · e0df8de4
      Andreas Marek authored
      Removed a forgotten C-preprocessor error flag.
      Futhermore, describe in the documentation why at the moment a
      build of Bluegene P/Q kernels and OpenMP is not allowed.
      e0df8de4