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

Looking for information on FIIfexp in Compaq Visual Fortran

crtillerson
Beginner
‎09-22-2009 11:31 AM
367 Views
Hello All,

I'm looking for general information on the internal routine FIIfexp using Compaq Visual Fortran and wondering if this issue will also persist as code is moved to recent versions of the Intel compiler.

We have code developed using the Compaq compiler in which the profiler in the IDE is showing a huge number of hits to FIIfexp ( 12 million ) which we assummed was due to the code referencing the EXP function. However, after all references in the code to EXP were commented out or replaced, the number of count/hits remained the same.

Runtimes are longer than expected, and we are looking at ways to optimize the code. An initial analyses lead us to first try and understand what this routine is for and how it is used.

Thanks for any insight you can offer!

Clint
0 Kudos

Link Copied

1 Reply
TimP
Honored Contributor III
‎09-22-2009 01:39 PM
367 Views
It's been a while, but surely that looks like ** exponentiation?
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.