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.
29285 Discussions

Per-subrroutine optimization level

Keith_R_
Novice
‎11-28-2002 02:31 PM
451 Views
I have a problem with a particular piece of code (which is not mine to simply rearrange at will) which causes ifc's optimizer to consume larger and larger amounts of memory until either it crashes (at -O3) or simply locks the machine up for 5 minutes paging (at -O2).

The code in question consists of very large nested case statement, which are actually machine-generated. To be fair to Intel, many other compilers exhibit exactly the same behaviour.

Is there any way of selectively reducing the optimization level for a single subroutine in a module? The Cray compilers had a directive to do this, and I wonder if anything similar exists for ifc.
0 Kudos

Link Copied

1 Reply
Martyn_C_Intel
Employee
‎12-19-2002 02:54 AM
451 Views
I don't know of a way to change the optimization level for just part of a module. I suggest you submit a small test case containing a very large, nested case statement to Intel Premier Support at https://premier.intel.com.
Of course, workarounds would not be difficult if you were able to change the source, or split the module.

Martyn
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.