vsldConvExec Windows 64-bit

[Philippe_Colliat]

Using Windows 7 64-bit, Visual Studio, licensed Intel Compiler, MKL libraries.

For some reason the vsldConvExec works fine under a 32-bit build on this machine but fails under a 64-bit build. I can build on this machine and take the binaries and it runs fine on another machine. Conversly I can build on another machine where it works fine, but copying those binaries to this machine does not work. I tried uninstalling Visual Studio and Intel compiler then reinstalling but that didn't fix anything.

Any tips are greatly appreciated.

[Gennady_F_Intel]

Philippe,

What is the CPU type you are working on? Can you get us the test for checking the problem? what MKL version you are using? What is your linking line?

--Gennady

[Philippe_Colliat]

There are now two computers identified that we are having difficulties with. Commonalities include:

- Previously had evaluation version of Intel compiler

- Previously only had 32-bit version of Visual Studio installed (both then uninstalled and reinstalled)

Machines' CPUs:

1)Intel Xeon E5405 (x2)

2) Intel Core 2 Duo P8600

MKL Version: 10.2 update 3

Linker line:

mkl_solver_lp64.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /OUT:"C:\dev\Projects\GPR\MissionUI\bin\Release\Exponent.Processing.dll" /INCREMENTAL:NO /nologo /LIBPATH:"C:\Program Files (x86)\Intel\Compiler\11.1\054\TBB\intel64\vc9\Lib" /LIBPATH:"C:\Program Files (x86)\Intel\Compiler\11.1\054\Lib\intel64" /LIBPATH:"C:\Program Files (x86)\Intel\Compiler\11.1\054\MKL\em64t\Lib" /MANIFEST /MANIFESTFILE:"x64\Release\Exponent.Processing.dll.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:"C:\dev\Projects\GPR\MissionUI\bin\Release\Exponent.Processing.lib" /MACHINE:X64 /DLL

I'll see if I can produce a small test that I can share soon.

[mmalmgrenexponent_co]

Here's a test that reproduces the problem we're having. I was able to hardcode about half of the parameters passed to vsldConvExec and the other ones are read in from a binary file that I've outputed from our working product.

If the test app runs cleanly it will display "Starting....Done" and also display the return value of vsldConvExec. If an exception does occur you will see "Exception caught while calling vsldConvExec!" and that is what we're seeing on the two machines mentioned above.

Let me know if there is anything else I can clarify.

[Gennady_F_Intel]

Philppe,

I couldn't reproduce the problem with the MKL v10.2 Update3 and 4.

the test dispays

"Starting ..Done"

one difference - I used CPUIntel Xeon CPU E5320 @ 1.86GHz

i will try to find out the similar CPU type which you used for checking this issue again

--Gennady

[Victor_Gladkikh · Accepted solution]

Hi Philippe,

I will recommend use MKL 10.2 update 4, because we have updates for Convolution and Correlation in MKL 10.2 update 4.

Victor

[Philippe_Colliat]

That solved the problem! It works on both computers that had the issue. Thanks so much.