[SOLVED] magma_dgesvd wrong optimal WORK array size ?

[ReL]

Hello,

When using magma_dgesvd I run into segfaults if I use the optimal WORK array size computed by the function in query mode.

This happens when M is at least N but not much larger (one way to reproduce is for example to use M = N). The formule used by magma_dgesvd is (M + N) * block_size + N, from my finding it seems that allocating (M + N) * block_size + 3*N elements fixes the problem.

I am not familiar enough with the code to check if the problem is really related to the optimal size formula or to an incorrect use of the work array.

Any idea on what I can be doing wrong or maybe what could be wrong on MAGMA side?

Thanks ! :)
Rémi

Edit: I forgot something important, the problem only happens with N > 128.

[Stan Tomov]

As you note the correct work space in real arithmetic is (M+N)*nb + 3*N. This bug in the documentation has been corrected in our SVN and will be available with the next release. The work space requirement for the complex versions is (M+N)*nb + 2*N.
Stan

[ReL]

That was fast, thanks a lot!