topic Version of MKL compatible with /SAFESEH in Intel® oneAPI Math Kernel Library

Version of MKL compatible with /SAFESEH

kenrussell — Fri, 10 Dec 2010 18:37:20 GMT

We compile our Windows executable with Visual Studio 2008 and the /SAFESEH linker option. When attempting to link against the MKL static libraries, we get dozens of errors like the following:

mkl_core.lib(_p4m_xdcopy.obj) : error LNK2026: module unsafe for SAFESEH image.

Removing the /SAFESEH option from our binaries works, but we don't want to do this. The documentation for linker error LNK2026 indicates that the modules in question need to be compiled with Visual C++ .NET 2003 or later. Is MKL built with Visual Studio or Intel's compilers? Would it be possible to have the Windows version of MKL be rebuilt so that it can be linked with executables using /SAFESEH?

Thanks.

Version of MKL compatible with /SAFESEH

Gennady_F_Intel — Sun, 12 Dec 2010 18:17:21 GMT

Yes, MKL is building by the Intel Compiler. What version are you talking about? We need to check this problem.

Version of MKL compatible with /SAFESEH

kenrussell — Mon, 13 Dec 2010 17:42:39 GMT

We are using the latest version of the MKL, 10.3.

Version of MKL compatible with /SAFESEH

Gennady_F_Intel — Thu, 16 Dec 2010 09:00:04 GMT

I didn't reproduce the problem. please see project attached as an example. This is the VS2008 solution linked with 10.3 version. Win32. static linking. I used the simplest function - cblas_caxpyi(,,,,);

--Gennady

Version of MKL compatible with /SAFESEH

kenrussell — Sat, 18 Dec 2010 02:01:28 GMT

The problem seems to be related to the use of the DFTI functions. Attached is a modified version of your project which reproduces the problem. The essential changes are in test.cpp so you can just pick those up. I also changed the linked libraries tomkl_intel_c.lib, mkl_sequential.lib, and mkl_core.lib, which is what we are using in our project.

Version of MKL compatible with /SAFESEH

Gennady_F_Intel — Tue, 21 Dec 2010 04:04:52 GMT

yes, I reproduced the problem with DFTI based example.

Would it be possible to have the Windows version of MKL be rebuilt so that it can be linked with executables using /SAFESEH?

We need to investigate the effort required to provide this capability and also any possible side-effects - primarily related to performance - that it might introduce.

--Gennady

Version of MKL compatible with /SAFESEH

kenrussell — Tue, 28 Dec 2010 22:49:48 GMT

We need to investigate the effort required to provide this capability and also any possible side-effects - primarily related to performance - that it might introduce.

Would it be possible to get a status update on this investigation? We intend to license the MKL, but this issue is a showstopper for our application.

Version of MKL compatible with /SAFESEH

Evgueni_P_Intel — Wed, 29 Dec 2010 11:41:23 GMT

Hi kenrussell,
We identified the root cause of this issue.
Weconsider fixing this issue in one of future MKL releases.

Version of MKL compatible with /SAFESEH

kenrussell — Wed, 05 Jan 2011 18:35:24 GMT

Quoting Evgueni Petrov aka espetrov (Intel)

Hi kenrussell,
We identified the root cause of this issue.
Weconsider fixing this issue in one of future MKL releases.

Thanks, that's great news.

Would it be possible to ask for a more precise time frame for the bug fix? All of the other alternatives we have, including using the DLL versions of the MKL, are really not desirable for our application.

Version of MKL compatible with /SAFESEH

Gennady_F_Intel — Tue, 01 Feb 2011 08:27:00 GMT

Hi Ken,

the problem has been fixed in the latest 10.3 Update2 which is available now. Please let us know if the any further issues will be discovered.

Regards,Gennady