As oneMKL's known issue, static linking on Windows can take significant time (up to 10 minutes) and linking static libraries can lead to a large application size due to GPU kernels.
It seems that oneMKL's feature has limited support. I see that the workaround exists with dynamic link; however, would you be able to tell me an estimate as to when this issue will be solved by any chance? Is there any other oneAPI library that has the same issue?
This problem is related to one MK only and is caused by some compiler issues. We are expecting the problem will fix in the next updates of oneMKL ( probably the next update 2), but there is not a final decision. Nevertheless, we will keep this thread inform when this problem will fix.
Thank you for your confirmation on the issue and plan for the fix in the future. I appreciate that you will keep this thread open. I look forward to hearing from you about the update.
The issue is closing and we will no longer respond to this thread. If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only.