- 28 Feb, 2020 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 21 Feb, 2020 1 commit
-
-
Andreas Marek authored
-
- 19 Dec, 2019 3 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
- 13 Dec, 2019 1 commit
-
-
Andreas Marek authored
-
- 10 Dec, 2019 3 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
- 04 Dec, 2019 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 20 Nov, 2019 1 commit
-
-
Andreas Marek authored
-
- 14 Nov, 2019 1 commit
-
-
Andreas Marek authored
-
- 11 Nov, 2019 1 commit
-
-
Andreas Marek authored
-
- 08 Nov, 2019 1 commit
-
-
Andreas Marek authored
-
- 05 Nov, 2019 1 commit
-
-
Andreas Marek authored
-
- 04 Nov, 2019 2 commits
-
-
Andreas Marek authored
Skew See merge request !26
-
Andreas Marek authored
-
- 31 Oct, 2019 1 commit
-
- 30 Oct, 2019 3 commits
-
-
Pavel Kus authored
-
-
Andreas Marek authored
Gitlab CI: Test for 64bit blas and 32bit MPI See merge request !24
-
- 29 Oct, 2019 1 commit
-
-
Andreas Marek authored
-
- 28 Oct, 2019 2 commits
-
-
Andreas Marek authored
-
Pavel Kus authored
This commit addresses several issues. It essentially forbids the use of the GPU kernel, which become obsolete and caused problems. But it does not complete remove the related code, nor does it forbid from explicitly selecting the GPU kernel. However, if the user does select it, the warning will be issued and the GENERIC kernel would be used instead. In the more details: * Commentin out operations in the GPU kernel, which do not compile with CUDA 10.1. This makes the kernel deffinitely not ussable (but it was true even before) * removing the gpu_tridiag_band option, sincie the tridiag->banded routine is actually not ported to GPU at all. This step will thus always be run on the CPU * removing the gpu_trans_ev_tridi_to_band option, since the GPU version of this step cannot run without the GPU kernel and it is not usable. This step will thus also be performed on the CPU * modifying REAL_GPU_KERNEL_ONLY_WHEN_GPU_IS_ACTIVE and COMPLEX_GPU_KERNEL_ONLY_WHEN_GPU_IS_ACTIVE such that the GPU kernel is not considered during the autotuning * TODO however, the GPU kernel can still be enforced by the user. In this case, during the calculation, a warning is issued and the kernel is switched to the GENERIC one. This should be improved and there should not even be the possibility to choose the GPU kernel at the begining.
-
- 26 Oct, 2019 2 commits
-
-
Andreas Marek authored
Long int scalapack See merge request !23
-
Andreas Marek authored
-
- 25 Oct, 2019 1 commit
-
-
Andreas Marek authored
-
- 24 Oct, 2019 7 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
Andreas Marek authored
-
Carolin Penke authored
-
Andreas Marek authored
-
- 23 Oct, 2019 3 commits
-
-
Pavel Kus authored
with cudaDeviceSynchronize
-
Andreas Marek authored
- 22 Oct, 2019 1 commit
-
-
Pavel Kus authored
a_dev was never freed on the GPU However, this might not be enough. What if bandred runs on GPU and band_to_tridi on CPU? a_dev is then not allocated. Has to be re-thinked in general
-