1. 11 Nov, 2019 2 commits
  2. 15 Oct, 2019 1 commit
  3. 10 Sep, 2019 1 commit
  4. 30 Jul, 2019 1 commit
  5. 16 Jul, 2019 1 commit
  6. 16 May, 2019 2 commits
    • Martin Bauer's avatar
      Removed IntelMPI Workaround from CMake · a1b603d4
      Martin Bauer authored
      - workaround seems to be not necessary any more, for recent IntelMPI versions
      - the workaround did not play with CMake's try_compile function, which tries to compile some test programs to check for compiler features
        The workaround added '-include mpi.h' to the compile flags, which are also used by try_compile, but try_compile does not set include directories with "-I"
        This lead to the problem, that for example the OpenMP flag was not correctly determined, since there the try_compile mechanism is used
      a1b603d4
    • Martin Bauer's avatar
      Support for Boost 1.70.0 and Python 3.7 · 33fe0883
      Martin Bauer authored
      33fe0883
  7. 25 Apr, 2019 3 commits
  8. 11 Apr, 2019 1 commit
  9. 03 Apr, 2019 1 commit
  10. 27 Mar, 2019 1 commit
  11. 26 Mar, 2019 1 commit
  12. 07 Mar, 2019 1 commit
  13. 18 Feb, 2019 1 commit
  14. 13 Feb, 2019 2 commits
  15. 22 Jan, 2019 1 commit
  16. 02 Nov, 2018 1 commit
    • Martin Bauer's avatar
      CUDA CMake - removed boost "isystem" modification · 3a78f7dc
      Martin Bauer authored
      - recent GCC version produce error when "-isystem /usr/include" is added
        to command line. Error is: '#include_next <math.h>' not found
      - the removed "hack" added the cuda include dir with "-isystem" to
        the CUDA compiler arguments to prevent warnings from boost header
        -> currently there seem to be no warnings generated from boost headers
           so "hack" is removed
      3a78f7dc
  17. 31 Oct, 2018 1 commit
  18. 24 Aug, 2018 1 commit
  19. 23 Aug, 2018 1 commit
  20. 09 Apr, 2018 1 commit
    • Michael Kuron's avatar
      Fix tests failing with new OpenMP on Intel compiler · 3ad4a4a1
      Michael Kuron authored
      - NearestNeighborFieldInterpolator::get needs to break out of all loops, just not the current one. While the test seemed to succeed anyway, it crashed with corrupted memory during exit when compiled with Intel 17 in Release mode.
      - FftTest should not use thread-unsafe RNG in parallel section. Otherwise the Intel 16 compiler crashes.
      - Revert to -openmp on Intel < 16.0.3, which crashes while processing some of our OpenMP loops (e.g. BoundaryHandling::treatDirection).
      3ad4a4a1
  21. 08 Apr, 2018 1 commit
  22. 14 Mar, 2018 2 commits
  23. 26 Feb, 2018 1 commit
  24. 21 Feb, 2018 1 commit
  25. 20 Feb, 2018 1 commit
  26. 14 Feb, 2018 3 commits
  27. 28 Jan, 2018 1 commit
  28. 27 Jan, 2018 1 commit
  29. 26 Jan, 2018 1 commit
  30. 12 Jan, 2018 1 commit
  31. 03 Jan, 2018 1 commit
  32. 20 Dec, 2017 1 commit