A compilation fails with a message similar to one of the following:

example.c(22): internal error:

Please visit 'http://www.intel.com/software/products/support' for assistance.

[ Aborting due to internal error. ]

compilation aborted for example.c (code 1)

or

catastrophic error: **Internal compiler error: internal abort**

Please report this error along with the circumstances in which it occurred in a Software Problem Report.

Note: File and line given may not be explicit cause of this error.

compilation aborted for example.f90 (code 3)

This message usually indicates a compiler defect.

Please report the problem to Intel through the Intel® Software Network Forums or Intel® Premier Support (support license and registration required). You will need to supply a test case along with a list of the compile options used and the exact compiler version that shows the problem. If you are not using a current compiler version, try the most recent version available to you as the error may have already been corrected.

Please note that this message is generic in nature and does not have a single cause nor solution. Providing a test case that reproduces the error is the only way to get a precise analysis of the problem.

In some, but not all, cases, you can work around the error by reducing the optimization level. You may find it helpful to try compiling with fewer switches to see if you can find one that, when removed, eliminates the error. It is also helpful to remove or comment out portions of the source file to see if you can isolate the line or lines that trigger the problem. The smaller the test case, the easier it will be for Intel to resolve the problem.

[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.]

template< typename Arg > void foo(Arg, void (*pf)(Arg)); // icpc does not deduce type of Arg in pointer to function class Bond {}; class Angle {}; void g(Bond); void g(Angle); void f() { foo( Bond(), &g); } 

$ icpc -V -c simple.cpp Intel(R) C++ Compiler for applications running on IA-32, Version 10.1 Build 20090203 Package ID: l_cc_p_10.1.022 Copyright (C) 1985-2009 Intel Corporation. All rights reserved. Edison Design Group C/C++ Front End, version 3.8 (Feb 4 2009 22:33:53) Copyright 1988-2006 Edison Design Group, Inc. simple.cpp(10): error: no instance of function template "foo" matches the argument list argument types are: (Bond, <unknown-type>) foo( Bond(), &g); ^ compilation aborted for simple.cpp (code 2)

Up to date Intel® compilers are available from the Intel® Registration Center under the Data Administration » Downloads and may be installed using any non-expired release, evaluation, or non-commercial license.

Support renewals for Intel® Software Development Products are available from local resellers or direct from Intel. Support renewals extend support for one year from the expiration date of your current support agreement.

You can log into the Intel Registration Center using your Intel® Premier Support account ID and password. If you forgot your login ID or Password, please select the link Forgot Password? appearing under the Registered users log in on the initial Intel Registration Center login web page.

For technical support, please visit Intel Software Product Support.

Please follow these guidelines when you submit a technical issue to Intel® Premier Support:

1. Submit the issue under the correct product.

   Binary Name Intel® Premier Support Product Name icl Intel® C++ Compiler for Windows* Intel® Parallel Composer ifort Intel® Fortran Compiler for Windows*, Intel® Fortran Compiler for Linux* or Intel® Fortran Compiler for Mac OS* icc, icpc Intel® C++ Compiler for Linux* Intel® C++ Compiler for Mac OS* idb Intel® C++ Compiler for Windows*, Intel® Fortran Compiler for Windows*, Intel® C++ Compiler for Linux*, Intel® Fortran Compiler for Linux*, Intel® C++ Compiler for Mac OS* or Intel® Fortran Compiler for Mac OS* (Choose the compiler that was packaged with idb.) ias Intel® C++ Compiler for Windows*, Intel® Fortran Compiler for Windows*, Intel® C++ Compiler for Linux*, Intel® Fortran Compiler for Linux*, Intel® C++ Compiler for Mac OS* or Intel® Fortran Compiler for Mac OS* (Choose the compiler that was packaged with ias.) ccxscce Intel® C++ Compiler for Windows*, Intel® C++ Compiler for eMbedded Visual C++*, or Intel® C++ Compiler for Platform Builder for Microsoft Windows* CE .NET (Choose the compiler that was packaged with ccxscce.) asxscce Intel® C++ Compiler for Windows*, Intel® C++ Compiler for eMbedded Visual C++*, or Intel® C++ Compiler for Platform Builder for Microsoft Windows* CE .NET (Choose the compiler that was packaged with asxscce.)

    

   Note: If you are reporting a problem for a beta version of the compiler and you were invited into the beta program for that compiler, submit your issue under the beta equivalent of the products listed above (e.g., Beta Intel® C++ Compiler for Windows*).
   
   
2. Enter the appropriate customer impact value.
   Customer impact values include Low, Medium, High, and Showstopper defined as follows (listed from least important to most important):
   
   
   • Low - An issue that has no significant impact and is submitted on a for-your-information basis.
     
     
   • Medium - An issue that does not stop development however needs to be fixed.
     
     
   • High - An issue with a short-term work-around, however needs to be fixed as soon as possible.
     
     
   • Showstopper - An issue that prevents you from using the compiler.
   
   
3. Give a complete problem description.
   
   3aInclude a description of the development environment:
   
   For Windows or Windows CE
   • Please provide a version number for each Intel Compiler installed on your platform. Version information can be obtained by making sure the /nologo compiler switch is removed. For the embedded compilers, this may necessitate removing /nologo from the ccxscce.cfg configuration file in the compiler bin directory. For example, to determine the version of the C++ compiler, please execute icl.
   • Please indicate the version of the Windows operating system and the version number of the latest service pack applied.
   • Please indicate the version of Microsoft Visual C++ and/or Studio and the version number of the latest service pack applied.
     
     
   For Linux
   • Please provide a version number for each Intel Compiler installed on your platform. Version information can be obtained by using the -V compiler switch. For example, to determine the version of the C++ compiler, please execute icc -V.
     
     
   • Please indicate the vendor name of the version of Linux* you're using.
     
     
   • Please indicate the Linux* kernel version number. Please execute cat /proc/version.
     
     
   • Please indicate the GNU* glibc version number. Please execute the package manager on your Linux system to obtain the glibc version number.For example, using RPM on Redhat, use the command rpm -qa|grep glibc.
     
     
   • Please indicate the GNU* gcc version number. Please execute gcc -v.
   
   For Mac OS
   • Please provide a version number for each Intel Compiler installed on your platform. Version information can be obtained by using the -V compiler switch. For example, to determine the version of the C++ compiler, please execute icc -V.
     
     
   • Please indicate the GNU* gcc version number. Please execute gcc -v.
     
     
   • Please indicate the Xcode* version number.
   
   For all systems
   
   
   • Please indicate if any additional programming software has been installed and version information.
   • Please indicate if any additional library programming software has been installe d and version information.
   
   3bProvide a reproducible test case with clear instructions, including compiler and linker options, on how to reproduce the problem you encountered.
   
   Submitting a test case that can be easily and quickly reproduced can make a real impact on resolution time. The goal is to submit as small a test case as possible. Submitting an entire application with possibly hundreds or thousands of source code files that reproduce the problem is an example of an unacceptable test case. Although this may reproduce the problem, setting up the application development environment and researching the issue will require too much time. Submitting a single large source code file (even if the file is large) or a small number of source code files that reproduce the problem encountered is crucial for resolving the problem encountered.
   
   Clear instructions include information like compiler and linker options and the exact error message and context to look for. For run-time issues, the problem report should include what good behavior looks like versus what bad behavior looks like. For performance issues, timing methods and results should be included. In all of these cases, please make an attempt to locate what part of the code is causing the problem, and let us know if you find that out. Other guidelines:
   
   
   • For compile-time or link-time problems, you can create a preprocessed .i file with the -P compiler option. This will include all header information and source code in one easy to manage file.
   • If your test case incorporates a makefile, please make sure it's executable with either Microsoft Visual Studio* nmake or GNU gmake facility. Also, please include all environment information since our environment may differ from yours. The importance is to insure dependence on path settings, third party utilities and libraries are accounted for and minimized.
   • If your problem is a compiler or linker error with C or C++, we provide the icpi utility to help narrow down small test cases. Preprocess the problematic source file with the -P compiler option, then rename the resulting .i file with the appropriate extension (.c, .cpp), and run icpi as described in the icpi.htm file in the compiler docs directory.