Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
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.
29280 Discussions

So when do you need new “mod” files

Carl_S_3
Beginner
‎04-04-2013 07:39 AM
428 Views

I am releasing some C++/ F90 libraries built with different versions of the compiler (9,11 and 12) and with different compiler options (let’s say release, debug, optimized).

Now being a C/C++ kinda guy,  I am used to looking at my “include” files and I know I need only one set of them….. but mod files are binary. So what makes you need a different one?

-          Does changing compiler options (i.e. debug)

-          Changes to the compiler

  • I assume major version change say from 11 to 12, but from 11.0 to 11.1?

-          Does bitness affect it? i.e. 32 vs 64 Bit?

-          Am I missing something?

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎04-04-2013 08:06 AM
428 Views

In most cases, you need new .mod files only when changing platforms (32-bit vs. 64-bit, Windows vs. Linux, etc.)  We try very hard not to require recompiling of old .mod files when used with newer compiler versions, but sometimes there are bugs or other changes that make it necessary. The release notes document these under "Compatibility". Debug vs. Release doesn't matter.

Note that you can't assume that .mod files compiled with a newer compiler can be used with an older one.

0 Kudos
Copy link
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.