-
Notifications
You must be signed in to change notification settings - Fork 32
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
Deprecation of 32-bit MKL in 2024.0 onwards. #128
Comments
It's |
Actually, hasn't MKL just been renamed to oneMKL? |
This is my understanding. When you interact with Intel, the MKL product seems to always be refered to as "oneMKL" and the GPU offload things are just a small part of the stack. And the main documentation page says (https://www.intel.com/content/www/us/en/docs/onemkl/developer-reference-c/2024-0/overview.html)
That said, I don't see the 32-bit deprecation notice in the release notes page right now, just the macOS removal notice. Has that page changed since the release to remove that notice? |
Should we document this (the deprecation of 32-bit) in the MKL.jl README somewhere? |
Ok, I found the deprecation notice inside the 2023.2.0 release notes here https://www.intel.com/content/www/us/en/developer/articles/release-notes/onemkl-release-notes-2023.html
It's a bit odd that the PGI support deprecation is announced in the 2023.2.0 release notes and repeated in the 2024.0.0 release notes, but that this 32-bit deprecation is not repeated. |
As @amontoison mentions - it deprecates 32 bit for oneMKL, which is for GPUs. We do not use that - we use MKL for CPUs. Hence nothing to document. |
I submitted a priority support request asking for clarification on this deprecation, and this is the response they gave:
So they say they aren't yet deprecated apparently but will be discontinued in the future (but don't actually say when). |
MKL 2024.0 will stop shipping 32-bit MKL: https://www.intel.com/content/www/us/en/developer/articles/release-notes/onemkl-release-notes.html
The text was updated successfully, but these errors were encountered: