Intel® oneAPI Math Kernel Library
Ask questions and share information with other developers who use Intel® Math Kernel Library.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
7234 Discussions

Size of executable (DLL) using MKL

netphilou31
New Contributor III
‎10-10-2012 06:53 AM
407 Views

Hi,

I have a project that was originally created using COMPAQ Visual Fortran. This project uses the IMSL library for doing cubic spline interpolations (AKIMA). I have recreated the same project (not converted the existing one from CVF) with VS1010 / Intel(R) Visual Fortran Compiler XE on IA-32, version 12.1.6 Package ID: w_fcompxe_2011.12.369 and I have replaced the use of IMSL by the MKL for the cubic spline calculations. It works nearly correctly except that I have noticed that the size of the DLL is about twice the size of the CVF DLL using IMSL. My question is: Why such an increase of the size? (I have used a static link in order to avoid the need to redistribute runtime dlls). If I remove (for testing purposes) the calls to the MKL the size drops down to a more acceptable size.

The sizes are :

  • CVF DLL with IMSL =   7 397 kB
  • IVF DLL with MKL  = 17 794 kB
  • IVF DLL w/o MKL   =   9 266 kB

Any idea on how to reduce the size or why the size is so big?

Best regards,

Phil.

0 Kudos

Link Copied

0 Replies
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.