MAGMA Forum

I couldn't exactly replicate the issue, but it seems there is a problem. Running memcheck finds an invalid memory reference, which indicates a bug in MAGMA. We'll look into it. Otherwise, use the cublas dtrsm. -mark > cuda-memcheck ./dtrsm ========= CUDA-MEMCHECK 1.000000 0.000000 0.000000 -0.400000...

The multiple definitions of functions is a bug. Those functions are used only for profiling, so you can safely change the calls from Mylapackf77_* to lapackf77_*, and delete the definitions of Mylapackf77_*. As for the linking errors, there is a cross-dependency between libmagma and libmagmablas. Us...

I'm confused by your matrices. You have the following matrices (note Magma is column-wise): A = [ 1, 3, 5 ] [ 2, 6, 9 ] [ 3, 8, 2 ] B = [ 3, 1, 4 ] [ 5, 7, 6 ] [ 7, 9, 2 ] The first question is, if your numbers are actually all real, why are you specifying them as complex? The second question is, th...

See the testing directory. Probably magma has to go before cuda & cublas. This is what works on my machines: # on Linux with MKL gcc -O3 -DADD_ -DGPUSHMEM=200 -fPIC testing_zgetrf.o -o testing_zgetrf \ lin/liblapacktest.a -L${MAGMA_DIR}/lib -lcuda -lmagma -lmagmablas -lmagma -L${MKLROOT}/lib/intel64...

Or just repeat -lmagma:

-lmagma -lmagmablas -lmagma

-mark

For LU, Cholesky, and QR, there is multi-GPU support which handles matrices that will fit in the combined memory of multiple GPUs. Set the environment variable MAGMA_NUM_GPUS to specify the number of GPUs to use, and call the normal CPU interface. For example: export MAGMA_NUM_GPUS=2 For LU and Chol...

We will look into it.
-mark

Have you tried the same modification that you added to MAGMA 1.0 rc5?
-mark

You can post it here, or email one of the developers directly. No, we don't yet have a bug tracking database.
-mark

See this post:
viewtopic.php?f=2&t=365&hilit=+sizeptr#p1208