Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Size of Executables

Robert_Gartner
Beginner
640 Views

Hello all,

Previously when using Visual Fortran version 10.1 when compiling code I found the exectuables to be approximately 450kb. Currently, while evaluating Visual Fortran 12.0 the executables seem to be 800kb+. I am curious ifthere isanything to account for increase in size?

0 Kudos
3 Replies
Steven_L_Intel1
Employee
640 Views
I'm not seeing that - are you doing a debug build, perhaps?
0 Kudos
jimdempseyatthecove
Honored Contributor III
640 Views
Interprocedural optimizaitons may be inlining more code. Turn IPO off then see what happens.

Jim Dempsey
0 Kudos
TimP
Honored Contributor III
640 Views
Interprocedural optimizaitons may be inlining more code. Turn IPO off then see what happens.

Jim Dempsey

The settings implicit in /Qip are set up and down on each compiler release to keep pace with various other compilers and platforms. /Qip- or more detailed use of the documented limits associated with /Qip will help control object size. In addition, /O1 usually makes much smaller code than the default; you forgot to tell us if you set /O1 in both cases.
Newer compilers also tend to do more auto-vectorization and multiple versioning. If you have a specific problem with multi-versioning hurting performance, you should file the example on premier.intel.com. You could compare the opt-report between the compiler versions to see whether these attempted optimizations are involved.
If a new vectorization is not useful for you, perhaps on account of your loop count not matching the assumed value of 100 (in the case where the compiler can't estimate it from the context), you should consider
!dir$ loop count(your expected value).
0 Kudos
Reply