Issue on page /elements/oneMKL/source/domains/lapack/lapack.html about oneapi-spec HOT 5 CLOSED

Hi @jakub-homola, thanks for the question! The matrices in the LAPACK domain are assumed to be column-major. You're right that we need to add this information to the oneMKL specification. Thanks for finding this!

from oneapi-spec.

Hi @jakub-homola,
When we introduced row major support for the BLAS domain, that was one consideration - to take a parameter that indicated the layout of the matrices (like in CBLAS/LAPACKE). However, we ultimately opted to create separate namespaces as typically an application would use just one layout for the whole application. With namespaces, you don't need to pass an extra layout parameter for every function.

from oneapi-spec.

@jakub-homola Thanks again for catching this! I appreciate your interest and thoughtful replies. As we've updated the specification to clarify this, I'd like to ask @mmeterel to close this issue. Please re-open if needed.

And just a note about Intel oneMKL documentation since that was mentioned in the initial report: We note that "Currently, LAPACK DPC++ APIs do not support matrices stored using row major layout." in the Intel® oneAPI Math Kernel Library (oneMKL) - Data Parallel C++ Developer Reference (link). However, we will make this more clear in a future update. Thanks again!

from oneapi-spec.

Assigning to @sknepper

from oneapi-spec.

Thanks for the reply.
However, when thinking about it, I think it would be better to add an additional oneapi::mkl::layout argument, rather than accepting only column-major matrices. Would it be possible, with respect to backwards compatibility?

from oneapi-spec.