-
Notifications
You must be signed in to change notification settings - Fork 747
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
Missing mkl_somatcopy and relatives #1331
Comments
Their symbols do appear to be defined in mkl_rt, but their declarations is no where to be found in the header files. How did you figure out their signatures? |
Ah, no, they seem to be available in "mkl_trans.h" these days. They used to have some strange macros attached, but that's now all in "mkl_trans_names.h" so as long as we don't try to parse that we should be fine. 🤔 |
I used a mkl.h that came with intel's MKL installation on linux. I was using the C API, though; wasn't aware that there could be something messed up in the C++ part... |
I've removed those lines in commit 41d9d2b and the builds are not failing, so it looks like there are no problems. |
It works, as expected. Thank you! |
Probably something like that, yes. |
Version 1.5.9 has been released! Thanks for reporting |
Hi,
I'm using JavaCPP 1.5.8, but judging by the generated mkl_rt.java in 1.5.9-SNAPSHOT= it is the same in the latest master.
I noticed that =mkl_rt= is missing the mkl_?omatcopy function that is defined in MKL and that is present in mkl_rt for years (similarly to #1326 ).
There is a difference, though, because judging by the JavaCPP MKL configuration source, this function should be available!
javacpp-presets/mkl/src/main/java/org/bytedeco/mkl/presets/mkl_rt.java
Line 67 in 138c9b0
What is also strange is that batched variants of mkl_?omatcopy are present! (mkl_rt/mkl_somatcopy_batch etc.)
The same problem is present with mkl_?omatadd..
BTW the mentioned functions are present and vailable in vanilla MKL; I've been using it via custom C JNI bindings for years.
The text was updated successfully, but these errors were encountered: