dfdNewTask1D crash (cont.d)

[netphilou31]

Hi,

This is a follow up of the post Re:dfdNewTask1D crash - Intel Community, since the original post has been closed for a reason I don't know, leaving some questions unanswered.

So, to answer to Shanmukh.SS last question, the update is:

I was able to solve my issue by adding the mkl_vml_p4.2.dll in the list of preloaded dlls. I guess that this dll can work with all of the processors (older and newer), whereas I was not sure for the library mkl_vml_avx512.2.dll.

I browsed the links you sent me but not in deep because I changed my mind on how to link with the MKL. I decided to enclose all the MKL functions I need into another dll which is statically linked with the MKL, so I probably won't have these issues anymore.

Best regards,

Phil.

[ShanmukhS_Intel]

Hi Phillippe,

Thanks for posting in Intel Communities.

I decided to enclose all the MKL functions I need into another dll which is statically linked with the MKL, so I probably won't have these issues anymore.

>> Sure, Please let us know if you face any challenges while trying to perform the same.

Best Regards,

Shanmukh.SS

[ShanmukhS_Intel]

Hi,

A gentle reminder:

Could you please let us know if there are any updates on your issue?

Best Regards,

Shanmukh.SS

[netphilou31]

Hi,

I was able to move the related functions and subroutines into another dll statically linked to the MKL. I tested this new dll with success. My next step will be probably to build a third dll which will contain all the functions I would need from the MKL and to statically link this dll with the latest version of the MKL. My concern is to still be able to call the 32-bit version once it will be removed from the installation package (in 2025 as you mentioned) in case we still have 32-bit applications at that time.

So, I think that this post can be closed but I would like to know if you've got some info about the original problem and if a future version will have a fix for it.

Best regards,

Phil.

[ShanmukhS_Intel]

Hi,

As the industry has largely shifted to 64-bit architecture over the last decade, Intel® oneMKL 32-bit binaries will be deprecated in the upcoming Intel® oneMKL 2024.0 release and targeted to be removed after one year deprecation notice period. If you are currently using the 32-bit binaries, please consider upgrading to our 64-bit options. You can share your feedback or any concerns on the oneMKL Community Forum or through Priority Support. 

So, I think that this post can be closed 

>>Sure, Thanks for letting us know. In case you run into any other issues please feel free to create a new thread.

Best Regards,

Shanmukh.SS