-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue on page /elements/oneMKL/source/domains/lapack/lapack.html #470
Comments
Assigning to @sknepper |
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! |
Thanks for the reply. |
Hi @jakub-homola, |
@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! |
Hi,
Are all the matrices in the LAPACK domain of oneMKL assumed to be row-major or column-major?
It seems they are assumed to be column-major, but I could not find that information anywhere on the webpage, nor there are any
oneapi::mkl::layout
parameters to the functions. Right now I am mainly concerned aboutpotrf
andtrtrs
, but knowing that information for the whole LAPACK would be great.Could you please redirect me to where I can find that information, or add it to the spec/docs?
The version of the spec I am seeing is 1.2-rev-1
The text was updated successfully, but these errors were encountered: