Cache MKL plans

[pfeatherstone]

This PR caches MKL plans. This substantially improves performance when using MKL sequential and MKL TBB. Not benchmarked with MKL RT but I expect the same results.

[pfeatherstone]

@davisking Ready for an initial review. Linking to libmkl_rt.so was broken. Mainly because by default it loads libmkl_intel_thread.so at runtime using dlopen which in turns requires openmp, specifically the intel version. If that's not in your link libraries it breaks at runtime. I think this behaviour is not desirable. What i found is if you're also linking to ffmpeg or other libraries, you're inadvertently linking to gomp. So you might not see the error. Though libmkl_intel_thread.so requires the intel openmp, not the GNU. So it was actually using the "wrong" symbols. So i changed the cmake BLAS stuff to link to one of

• MKL sequential
• MKL tbb
• MLL thread (openmp)
  With MKL thread you explicitly link to openmp at link-time. It doesn't use dlopen. I think that's better.
  This required me to refactor the find_blas.cmake script which was a mess to be honest. I've also added some jobs to Github Actions to test all three version of MKL. The build_cpp.yml script needs some serious refactoring but that can be for another PR.

For the BLAS stuff i'm now using cmake_dependent_option which simplifies the super messy logic in the CMakeLists.txt script.

[pfeatherstone]

@davisking Do you mind having a look at this? Or are you wanting to merge the CUDA stuff first? I would rather get this in before i touch cmake revamping stuff again as I would be duplicating certain things in here already.

[pfeatherstone]

@davisking hold fire on merging. I haven't got the windows jobs working correctly with openblas and MKL. vcpkg takes too long to install those deps and haven't figured out how to use it correctly with cmake.

[pfeatherstone]

Right, i'm gonna need some help. I don't have a windows machine i can use for dev. I'm giving up trying to debug the windows builds simply by looking at github actions logs.

[dlib-issue-bot]

Warning: this issue has been inactive for 35 days and will be automatically closed on 2025-10-16 if there is no further activity.

If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search.

[dlib-issue-bot]

Warning: this issue has been inactive for 42 days and will be automatically closed on 2025-10-16 if there is no further activity.

If you are waiting for a response but haven't received one it's possible your question is somehow inappropriate. E.g. it is off topic, you didn't follow the issue submission instructions, or your question is easily answerable by reading the FAQ, dlib's official compilation instructions, dlib's API documentation, or a Google search.

[dlib-issue-bot]

Notice: this issue has been closed because it has been inactive for 45 days. You may reopen this issue if it has been closed in error.