Scheduled maintenance on Monday 2019-06-24 between 10:00-11:00 CEST

Prepare release candidate rc1 of ELPA-2019.05.001

- updated INSTALL
- change the ELPA vesioning number
- update Changelog and RELEASE_NOTES
parent 8d1057cc
Changelog for upcoming release
- user can define the default kernels
- simple block4 and block6 real kernel
- not yet decided
Changelog for ELPA 2019.05.001.rc1
- elpa_print_kernels supports GPU usage
- fix an error if PAPI measurements are activated
- new simple real kernels: block4 and block6
- c functions can be build with optional arguments if compiler supports it
(configure option)
- allow measurements with the likwid tool
- users can define the default-kernel at build time
- ELPA versioning number is provided in the C header files
Changelog for ELPA 2018.11.001
- improved autotuning
......
......@@ -49,7 +49,8 @@ An excerpt of the most important (*ELPA* specific) options reads as follows:
| configure option | description |
|:------------------------------------ |:----------------------------------------------------- |
| --disable-legacy | do not build legacy API, will be build as default |
| --enable-legacy-interface | build legacy API, will not be build as default |
| --enable-optional-argument-in-C-API | treat error arguments in C-API as optional |
| --enable-openmp | use OpenMP threading, default no. |
| --enable-redirect | for ELPA test programs, allow redirection of <br> stdout/stderr per MPI taks in a file <br> (useful for timing), default no. |
| --enable-single-precision | build with single precision version |
......@@ -57,6 +58,7 @@ An excerpt of the most important (*ELPA* specific) options reads as follows:
| --disable-band-to-full-blocking | build ELPA2 with blocking in band_to_full <br> (default:enabled) |
| --disable-mpi-module | do not use the Fortran MPI module, <br> get interfaces by 'include "mpif.h') |
| --disable-generic | do not build GENERIC kernels, default: enabled |
| --enable-sparc64 | do not build SPARC64 kernels, default: disabled |
| --disable-sse | do not build SSE kernels, default: enabled |
| --disable-sse-assembly | do not build SSE_ASSEMBLY kernels, default: enabled |
| --disable-avx | do not build AVX kernels, default: enabled |
......@@ -72,14 +74,17 @@ An excerpt of the most important (*ELPA* specific) options reads as follows:
| --with-fixed-real-kernel=KERNEL | compile with only a single specific real kernel. |
| --with-fixed-complex-kernel=KERNEL | compile with only a single specific complex kernel. |
| --with-gpu-support-only | Compile and always use the GPU version |
| --with-likwid=[yes|no|PATH] | use the likwid tool to measure performance (has an performance impact!), default: no |
| --with-default-real-kernel=KERNEL | set the real kernel KERNEL as default |
| --with-default-complex-kernel=KERNEL| set the compplex kernel KERNEL as default |
| --enable-scalapack-tests | build SCALAPACK test cases for performance <br> omparison, needs MPI, default no. |
| --enable-autotuning | enables autotuning functionality, default yes |
| --enable-c-tests | enables the C tests for elpa, default yes |
| --disable-assumed-size | do NOT use assumed-size Fortran arrays. default use |
| --enable-scalapack-tests | build also ScalaPack tests for performance comparison; needs MPI |
| --disable-Fortran2008-features | disable Fortran 2008 if compiler does not support it |
| --enable-pyhton | build and install python wrapper, default no |
| --enable-python-tests | enable python tests, default no. |
| --disable-assumed-size | do NOT use assumed-size Fortran arrays. default use |
| --enable-scalapack-tests | build also ScalaPack tests for performance comparison; needs MPI |
| --disable-Fortran2008-features | disable Fortran 2008 if compiler does not support it |
| --enable-pyhton | build and install python wrapper, default no |
| --enable-python-tests | enable python tests, default no. |
We recommend that you do not build ELPA in its main directory but that you use it
......
......@@ -2,20 +2,17 @@ This file contains the release notes for the ELPA 2019.05.001.rc1 version
What is new?
-------------
For detailed information about changes since release ELPA 2018.05 please have a look at the Changelog file
For detailed information about changes since release ELPA 2018.11 please have a look at the Changelog file
- improved autotuning
- improved performance of generalized problem via Cannon's algorithm
- check pointing functionality of elpa objects
- store/read/resume of autotuning
- Python interface for ELPA
- more ELPA functions have an optional error argument (Fortran) or required
error argument (C) => ABI and API change
- user can define a default kernel at build time
- ELPA VERSION number is exported to the C-header
- C functions can have an optional error argument, if compiler supports this
=> ABI and API change
ABI change
---------------------
Since release 2018.05.001 the ABI has changed.
Since release 2018.10.001 the ABI has changed.
Any incompatibilities to previous version?
---------------------------------------
......
......@@ -39,11 +39,11 @@ AC_SUBST([$1], ['$2'])
# API Version
AC_DEFINE([EARLIEST_API_VERSION], [20170403], [Earliest supported ELPA API version])
AC_DEFINE_SUBST(CURRENT_API_VERSION, 20181113, "Current ELPA API version")
AC_DEFINE_SUBST(CURRENT_API_VERSION, 20190524, "Current ELPA API version")
# Autotune Version
AC_DEFINE([EARLIEST_AUTOTUNE_VERSION], [20171201], [Earliest ELPA API version, which supports autotuning])
AC_DEFINE([CURRENT_AUTOTUNE_VERSION], [20181113], [Current ELPA autotune version])
AC_DEFINE_SUBST(CURRENT_AUTOTUNE_VERSION, 20181113, "Current ELPA autotune version")
AC_DEFINE([CURRENT_AUTOTUNE_VERSION], [20190524], [Current ELPA autotune version])
AC_DEFINE_SUBST(CURRENT_AUTOTUNE_VERSION, 20190524, "Current ELPA autotune version")
AX_CHECK_GNU_MAKE()
if test x$_cv_gnu_make_command = x ; then
......
AC_PREREQ([2.69])
AC_INIT([elpa_test_project],[2018.11.001], elpa-library@rzg.mpg.de)
elpaversion="2018.11.001"
AC_INIT([elpa_test_project],[2019.05.001.rc1], elpa-library@rzg.mpg.de)
elpaversion="2019.05.001.rc1"
AC_CONFIG_SRCDIR([src/test_real2.F90])
AM_INIT_AUTOMAKE([foreign -Wall subdir-objects])
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment