Hi,
I compiled an executable using Visual Studio Community 2015 with Intel Parallel Studio XE 2016 (Student License).
Very interesting, if set Use Intel MKL as "sequential" in Configuration Properties->Intel Performance Libraries->Intel Math Kernel Library, then it runs normally. If I set it as No, then it gives me an application error "0xc000007b".
Even confusing, if I compiled the codes by setting it as "sequential", when I double click the executable, it gives me same above application error. Note that I have set the environment variable: C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016\windows\redist\ia32\mkl
Anybody has a clue on how to successfully run the executable?
Link Copied
Hi Wei,
Could you please send the small test case or the exe to us so we can see what wrong?
According to your message , If I set it as No, then it gives me an application error. generally,
If I set it as No, then it gives me an application error . Generally, if mkl is not linked, you should get the compilation error, like
mkl.h is not found
or below
1>------ Build started: Project: matrix_multiplication_c, Configuration: Debug Win32 ------
1>dgemm_with_timing.obj : error LNK2019: unresolved external symbol _cblas_dgemm referenced in function _main
1>dgemm_with_timing.obj : error LNK2019: unresolved external symbol _dsecnd referenced in function _main
1>dgemm_with_timing.obj : error LNK2019: unresolved external symbol _MKL_malloc referenced in function _main
1>dgemm_with_timing.obj : error LNK2019: unresolved external symbol _MKL_free referenced in function _main
1>C:\Users\yhu5\Desktop\11.3\matrix_multiplication_c\Debug\matrix_multiplication_c.exe : fatal error LNK1120: 4 unresolved externals
There is one C and fortran sample code under MKL install forder, for example, C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.2.180\windows\mkl\samples. You can build it as test case. or
I attach one, could you please try it and let me know the output when compile. with or without "sequential"
Best Regards,
Ying
For more complete information about compiler optimizations, see our Optimization Notice.