MAGMA Forum

No, there isn't any particular reason, svd_gpu routines just haven't been developed. Thanks for the request; we'll consider them for future developments.
-mark

Have you tried the latest MAGMA 2.5.1 alpha 1? It should resolve many compiling issues from 2.5.
https://icl.utk.edu/magma/software/index.html
Mark

For complex matrices: magma_[cz]heevd* uses divide-and-conquer magma_[cz]heevr* uses MRRR magma_[cz]heevx* uses QR iteration if MagmaRangeAll, or bisection if MagmaRangeV or MagmaRangeI. For real matrices, only divide-and-conquer is available: magma_[sd]syevd* BTW, MAGMA is at version 2.5, not 2.0. ...

https://icl.utk.edu/magma/software/

Also the Mercurial repo at
https://bitbucket.org/icl/magma

-mark

Easiest to redirect the output:

MAGMA won't affect your computers performance while it is not running. While it is running, it will use the processor and GPU, so other programs would run slow. This is expected.
-mark

As for setting up a new source file for use in CMake, you need to run `make generate` or `make CMake.src`. I'm not sure why CMake wouldn't find `control/magma_sauxiliary.cpp`. What version of MAGMA are you using? Or did you get MAGMA directly from the bitbucket repo? Possibly the `make generate` wou...

Also, you can compile using `make magmablas/dstddev_mean.o` (from the top magma directory) to compile a single file to see if it is working, without recompiling the entire library. E.g., mint ~/Documents/magma> make magmablas/dznrm2.o nvcc -m64 -O3 -DNDEBUG -DADD_ -Xcompiler "-fPIC -Wall -Wno-unused...

Currently, CMake won't see new files. They have to be added with `make` first, which will generate magma/CMake.src. MAGMA uses a precision generator (magma/tools/codegen.py) to generate all 4 precisions (s, d, c, z for single, double, complex-single, complex-double) from, usually, the complex-double...

Shouldn’t matter, as long as they support CUDA. See Nvidia’s site.

Mark