Reference Number : DPD200178014


Version : IDB for Mac OS* X 10.7 Lion, v12.1 ( Updates 6, 7, 8, and possible future updates)


Product : Composer XE 2011 for Mac OS* X


Operating System : Mac OS* X 10.7


Problem Description : IDB debugger does not load default images produced by IFORT or ICC/ICPC:
"Could not start process for ...
No image loaded ... Recovering ... "



Resolution Status :

Mac OS* X Lion, by default, defaults to building executables with Position Independent Executable (PIE) code.  However, the Intel IDB debugger does not currently (as of Composer XE 2011 Updates 6, 7, 8, and 9) support debugging of PIE executables. 

To work around this, IFORT and ICC/ICPC can be directed to produce non-PIE executables.  The following options are required to produce an executable that IDB can process:

-g -save-temps -fpic -Wl,-no_pie

This affects the Intel Composer XE 2011 compilers running on Mac OS* X 10.7 Lion ONLY.  Users of Mac OS* X 10.6 (Snow Leopard) or 10.5 (Leopard) are not affected and need only the -g -save-temps options for creation of debuggable executables.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Introduction : The Intel C++ and Fortran compilers for Windows* and Linux* provide 'legacy' and 'compatibility' implementations of the OpenMP THREADPRIVATE directive (-Qopenmp-threadprivate:[compat | legacy], -openmp-threadprivate [compat | legacy]).  The 'compat' option should not be used when everything is compiled by Intel compilers. Doing some may result in application crashes or incorrect results. In this case, the 'legacy' option (which is the default) should be used.  The 'compat' option should only be used when some of the objects in an application have been compiled by a compatible Microsoft* or GNU* compiler.

Version : 11.x, 12.x


Application Notes : -Qopenmp-threadprivate:legacy (-openmp-threadprivate legacy) is the default when -Qopenmp (-openmp) is specified.  This setting does not provide compatibility with the THREADPRIVATE implementation used by other compilers. -Qopenmp-threadprivate:compat (-openmp-threadprivate compat) can be used when some of the objects in an application have been compiled by a compatible Microsoft* or GNU* compiler.  This setting provides compatibility with the implementation provided by the Microsoft* and GNU* compilers.


Building the Application : -Qopenmp (-openmp) must be given when using -Qopenmp-threadprivate (-openmp-threadprivate), or the compiler will not recognize the OpenMP THREADPRIVATE directive (warning #161: unrecognized #pragma).


Known Issues or Limitations : On Mac OS* X systems, 'legacy' is the only type of THREADPRIVATE implementation supported. Option '-openmp-threadprivate' is not recognized by the compiler.

Operating System : Mac OS* X 10.7 aka "Lion"


Support Status: July 19, 2011

Intel Fortran Composer XE 2011 for Mac OS* X and the Intel C++ Composer XE 2011 for Mac OS* X do not officially support use under Mac OS* X 10.7 "Lion". This also applies to official support for integration into Xcode 4.1 - this configuration is not supported at this time.

At this time Intel does not officially support use under Mac OS* X 10.7 and/or integration into Xcode* 4.1.

Compilers versions 11.1 and older are known to NOT work under Lion, and these older compilers will not be updated to work for Lion.

A future update of the 12.x compiler will support Lion, but the currently released 12.0 Update 4 also does NOT support Lion.

Do not upgrade to Lion if you need a working Intel compiler until we officially support Lion.

Official Intel compiler support for Lion will occur sometime after official release of Lion by Apple, whenever that may be.  Typically, Intel attempts to have a compiler update or release to support a major Mac OS* X release within 3 months or less of official launch.  Intel will alert customers to official support in the Release Notes of a compiler update or major release along with notices on our User Forums:

C++ User Forum:  http://software.intel.com/en-us/forums/intel-c-compiler/
Fortran Linux/Mac User Forum:  http://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/

While official support is currently not available, users may find that their existing Intel compilers for Mac OS X may or may not work as expected in this environment.  We do begin early testing during beta phases of Lion and will attempt to make our compilers compatible as soon as possible after official release.  Official support will follow official release of Lion and sufficient time to qualify our compilers under the officially released OS, and must synchronize with our internal release schedules for the compilers.  Again, typically this is 3 months or less after official OS release.

Fortran Note:  The Intel Fortran compiler integration into Xcode is a "Limited Feature", meaning that not all functionality within Xcode is available to Fortran users.  In particular, module dependencies are not detected and not respected: a user must manually compile modules in dependency sequence.  Also, the built-in Xcode debugger is not Fortran language aware, making debug rudimentary and problematic.  These and other current "Limited Feature" Fortran integrations into Xcode are also expected in the integration into Xcode 4.1.  This does not apply to users of Intel C++ for Mac OS X.

ADDITIONAL INFORMATION:

For a complete list of support resources, Forum, Downloads, Licensing, and other resources for Intel Fortran Compiler for Mac OS* X, visit our Knowledge Base here:  http://software.intel.com/en-us/articles/intel-fortran-compiler-for-mac-os-x-kb-home/

For a complete list of support resources, Forum, Downloads, Licensing, and other resources for Intel C/C++ Compiler for Mac OS* X, visit our Knowledge Base here:  http://software.intel.com/en-us/articles/intel-c-compiler-for-mac-os-x-kb-home/

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Problem : I compile a program on a Mac OS X 10.6 system, but run the binary on an older Mac OS X system such as 10.5 or 10.4.  The program aborts immediately without starting with error "dyld:  unknown required load command 0x80000022"


Environment : Mac OS X, mixed OS versions.  Intel Fortran Compiler for Mac OS X, Intel C++ Compiler for Mac OS X


Root Cause :
Generally, if you are targeting your applicaiton to run on multiple versions of Mac OS X, you should use the 'least common denominator' approach of developing on the older OS version.  This is because newer version may have extended the base OS API but generally newer versions will maintain backwards compatibility.

Resolution :
Although there is no guarantee for backwards compatibility, if you have a newer version of Mac OS X as your development platform, follow these guidelines:

compile and link with option   -static-intel   ( for older compilers, -i-static )
Pass linker option:     -Wl,-macosx_version_min,10.4
so
ifort -static-intel -Wl,-macosx_version_min,10.4   ...other options...
icc -static-intel -Wl,-macosx_version_min,10.4   ...other options...
icpc -static-intel -Wl,-macosx_version_min,10.4   ...other options...

The -static-intel will statically link all Intel compiler runtime libraries into your executable so that you will not need these DYLD libraries on the target computer.

The -Wl,-macosx_version_min,10.4  passes the argument  -macosx_version_min 10.4

to your ld linker.  This tells the linker to create headers and sections for the executable that are backwards compatible to Mac OS X 10.4.  Another option might be 10.5.  Please read your 'ld' man page or documentation for allowed options.

EXCEPTION:  the linker provided with Xcode 4.0.1 on Snow Leopard is rejecting the -macosx_version_min option, although it is documented in the 'ld' man page.  We believe this is a recent bug in the Apple linker and hope that it is addressed shortly ( Apr 2011 )