Intel® Moderncode for Parallel Architectures
Support for developing parallel programming applications on Intel® Architecture.
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.
1699 Discussions

plain function names in binaries when using OpenMP

rakkota
Novice
‎01-25-2013 09:05 AM
630 Views
Hi, I found that function names appear as is in the release binaries if a OpenMP loop has been defined inside. Moreover, paths from the build machine and code line numbers are also indicated. For example, using FORTRAN compiler 10.0.025 in an executable I've got: ;D:\cygwin\home\build\dev\tags\emme2\GR\GR-3.3.1\bin\msvc-9.0\release\link-static\threading-multi\modaux522.f;_MODSUBPROBLEMCL1PAR_mp_SUBPROBLEMCL2TO12PAR;1096;1096;; Using FORTRAN Composer 13.0.0.1 in a dll I've got: ;unknown;_STEP523_SE;1060;1111;; Is there a way to avoid this? Why OpenMP need plain names or code line numbers in the executable that are compiled in release mode? Thanks, Rak
0 Kudos

Link Copied

2 Replies
TimP
Honored Contributor III
‎01-25-2013 07:27 PM
630 Views

I think this has been discussed previously on one of the Fortran forum sections.  In the 10.0  compiler, one of the evident reasons for this was to enable openmp-profile.

0 Kudos
Copy link
rakkota
Novice
‎01-28-2013 06:38 AM
630 Views

TimP (Intel) wrote:

I think this has been discussed previously on one of the Fortran forum sections.  In the 10.0  compiler, one of the evident reasons for this was to enable openmp-profile.

Thanks for the explanation. Can this be disabled?

Rak

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.