The questions summarized in this section address post-installation troubleshooting or usage issues that apply to this compiler. For information on troubleshooting during application development, see Troubleshooting Your Application.
| Question | Discussion |
|---|---|
|
How do I Invoke the compiler? |
Answer: The Getting Started document gives detailed instructions on configuring, setting environment variables, and invoking your Intel compiler. Note that most compilers support both command-line and Integrated Development Environment (IDE) versions. Applicability: IA-32, IA-64, Intel® 64 architectures; Operating System - Windows, Linux, Mac OS; Language - C++, Fortran More Detail: Refer to the product Release Notes and Installation Guide for additional invocation information. Refer the Getting Started topics in the compiler User Documentation for detailed information for your compiler. |
|
What are the processor-specific compiler options for Intel compilers? |
Answer: The /Qx option (Windows*) and -x option (Linux* and Mac OS*) generate processor-specific instructions. These options generate some specialized code for specific Intel processors that can result in better performance on specific Intel processors for some types of applications. Applicability: IA-32 and Intel® 64 architectures; Operating System - Windows, Linux; Language - C++, Fortran More Detail: Refer to the Building Applications and Optimizing Applications sections of the compiler online documentation for detailed information for your compiler. |
|
How can I resolve a LNK2001:unresolved external symbol __security_check_cookie on Windows* 2003 RC1 message? |
Answer: This applies to Microsoft Windows Server 2003 with Service Pack 1 SDK - RC1 (Build 1289) and later. The work-around is to link with the bufferoverflowU.lib, bufferoverflowK.lib, or bufferoverflow.lib library or use /MD (for example: icl hello.c /MD). Applicability: IA-64 architecture; Operating System - Windows; Language - C++, Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/c/windows/sb/CS-020442.htm for a more detailed answer. |
|
How can I address "New Calling Convention Used in Windows* Server 2003 x64 RC1 (Bld 1289) or Newer" issues? |
Answer: Changes to Windows* 2003, x64 Edition - RC1 (Build 1289) and Microsoft Windows Server 2003 SP1 Platform SDK (Build 1289 or later) calling conventions affect the saving and restoring of XMM registers used in SSE, SSE2, and SSE3 code between function calls. If you are using Intel compilers for Intel® 64 architecture on Windows*, then upgrade to, and rebuild with, new Intel® C++ version 8.1.025 or later and Fortran Compilers for Windows* version 8.1.028 or later, Intel® 64 architecture editions. Applicability: Intel® 64 architecture; Operating System - Windows; Language - C++, Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/c/windows/sb/CS-020438.htm for a more detailed answer. |
|
How is the OpenMP* specification supported in Intel compilers? |
Answer: The Intel Compilers 9.1 (and later) supports version 2.5 of the OpenMP* specification. There are some qualifications and limitations associated with this support as noted in the solution web page. Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System -Windows, Linux, Mac OS; Language - C++, Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/c/linux/sb/cs-007720.htm for a more detailed answer. |
|
What are the compatibility and software requirements for Intel compilers working with Microsoft Visual Studio? |
Answer: The compatibility and software requirements for each compiler with respect to working with Microsoft Visual Studio are described in the product Release Notes. Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows; Language - C++, Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/c/windows/sb/cs-007750.htm for a more detailed answer. |
| Why do I get the message "Error: could not find 'link'"? | Answer: This error message is referring
to the Microsoft Visual C++* linker and libraries, which are required
to link objects compiled by the Intel® Fortran Compiler for Windows*.
An appropriate linker is installed when the correct
Microsoft product (for IA-32 architecture; Microsoft Visual C++* .NET
2003, Visual Studio* .NET 2003, Visual Studio 2005, or Visual C++
2005: for Intel® 64 or IA-64 architectures; Microsoft Visual Studio 2005
or Microsoft Platform SDK).
Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows; Language - Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/fortran/windows/sb/cs-007858.htm for a more detailed answer. |
| Why does the linker not find the dfor.lib or dfconsol.lib files? |
Answer: All Compaq* Visual Fortran (CVF)-compiled Fortran code must be recompiled. Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows; Language - Fortran More Detail: Refer to the Intel® Visual Fortran Community Forum to ask "how to" questions of other users. Technical support for Compaq* Visual Fortran is offered by Hewlett-Packard* via the Compaq Visual Fortran Support e-mail address. |
| What does "array bounds error" mean? | Answer: Bounds expression variables
must be declared before use. The Intel® Fortran Compiler enforces the
bounds rule of the Fortran language standard and gives an error if it
is violated.
Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows, Linux, Mac OS*; Language - Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/sb/CS-022388.htm for a more detailed answer. |
| Are the Intel libraries for Intel compilers thread safe? |
Answer: The C++ libraries, with the exception of libirc.a, are thread safe. The Fortran libraries, with the exception of libirc and libifccore, are thread safe. Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Linux, Mac OS; Language - C++, Fortran More Detail: Refer to the Software
Product Support solution at http://www.intel.com/support/performancetools/c/linux/sb/cs-007728.htm
for a more detailed answer on C++. |
| Why is an icc, icpc, or ifort command not recognized? |
Answer: In the Linux environment you need to do the appropriate "source" command. The Getting Started document gives detailed instructions on configuring and setting environment variables for Intel compiler. Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows, Linux; Language - C++, Fortran More Detail: Refer to the product Release Notes and Installation Guide for additional invocation information. Refer to the Getting Started topics in the compiler User Documentation for detailed information for your compiler. |
|
How do I build mixed-language applications in Visual Studio? |
Answer: In Microsoft Visual Studio* 6.0 it was possible to have a project that contained both C++ and Fortran source files. In Microsoft Visual Studio .NET it is not possible to have mixed languages within the same project. To work around this issue, create separate projects within a Visual Studio .NET solution, one or more containing your C++ source and one or more containing your Fortran source. Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows; Language - C++, Fortran More Detail: Refer to the Software
Product Support solution at http://www.intel.com/support/performancetools/c/windows/sb/cs-007742.htm
for a more detailed answer on C++. |
|
How do I begin running my program under the Visual Studio debugger? |
Answer: For full support of Microsoft Visual Studio* 2005, you should install the 9.1 or 10.0 version of the Intel® C++ Compiler or Intel® Visual Fortran Compiler. Earlier versions of the Intel® Debugger as well as the Intel® C++ or Intel® Visual Fortran compiler must be uninstalled before you can start the Microsoft Visual Studio* 2005 IDE debugger. Failure to do so will result in an error indicating "MSDIA80.dll cannot be loaded". Applicability: IA-32, Intel® 64, IA-64 architectures; Operating System - Windows; Language - C++, Fortran More Detail: Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/fortran/windows/sb/CS-007848.htm for a more detail on Visual Studio. Refer to the Software Product Support solution at http://www.intel.com/support/performancetools/sb/CS-022760.htm for a more detailed answer on the debugger. |