MAGMA Forum

Thanks for these documentation bug reports! We fixed them in the SVN. Regarding the hvector question, you are right, it is on the CPU memory. An example on how to use the routine is in testing_dsgeqrsv_gpu.cpp. This routines tests mixed precision, as well as working precision solvers like the magma_...

Hello, I can confirm there is an issue. There is a bug related to the error checking, and in particular, the size of a pivot array piv in err = magma_malloc_cpu( (void**) &piv, N*sizeof(magma_int_t) ); assert( err == 0 ); should have been Ak, as in err = magma_malloc_cpu( (void**) &piv, Ak*sizeof(ma...

Thanks for pointing this out! We will fix it for the next release.

Thanks for pointing this out. We had other user requests and feedback on the testers and we redesigned them. They are more uniform looking now and support -h option to print help. Different options give the user a way to specify specific sizes, ranges, error checking, etc. This will be available wit...

The ultimate goal is that the user would specify what hardware to be used (while the default would be to use everything available). This is not possible right now but we keep adding functionality that would make it possible, e.g., we released clMAGMA for enabling MAGMA use on any accelerator through...

Try linking with these libraries or consult with the MKL's link adviser at http://software.intel.com/sites/products/mkl/
Stan

Upon further investigation we found that the problem is with Intel's compiler. This CUDA release note summarizes the issue: There is a known bug in ICC with respect to passing 16-byte aligned types by value to GCC-built code such as the CUDA Toolkit libraries (e.g., CUBLAS). At this time, passing a ...

This routine becomes more compute intensive when eigenvectors are needed. In that case most of the flops are in gemm and this is what is GPU accelerated.
Stan

Hi,
This is just for convenience in maintaining the codes in different precisions. We keep one version in double complex and generate all the rest with a python script. Besides this there is no other reason to have two macros.
Stan

Hello,
I think the bug is actually in the example file, in particular, you have used expressions like sizeof(x1), which in your case is 32 (4 doubles), instead of sizeof(x[0]) or just sizeof(double).
Stan