What you should know before requesting technical 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.

    3a
    Include 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.

    3b
    Provide 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.
If you are ready to submit issues, please go to the Intel® Premier Support web page.
For more complete information about compiler optimizations, see our Optimization Notice.