New in Intel® C++ Compile 11.1 Integration in Microsoft* Visual Studio*

• Intel® Parallel Debugger Extension is added and a new toolbar -
• Documentation is integrated into Visual Studio IDE
  • .chm documentation is also available and accessible from Start menu.
• New project properties for parallel lint options
• New project property for using Parallel Debugger Extension
• Intel C++ Compiler toolbar enhanced with a new icon to set include & link directories for IPP & TBB -

New in Intel® C++ Compile 11.0 Integration in Microsoft Visual Studio

• Support the native Intel® 64 compiler
• New project properties for Source Verifer feature under "C/C++->Diagnostics"
• New project properties for enabling different level of optimization diagnostics under "C/C++->Diagnostics"
• New Profile Guided Optimization menu under "Project"
• Support "continue on error" for compilation
• Added automation interfaces for manifest tool

New in Intel® C++ Compile 10.1 Integration in Microsoft Visual Studio

• Support Visual Studio 2008* from compiler update w_cc_p_10.1.020 or newer
• Improved support of the manifest feature

New in Intel® C++ Compiler 10.0 Integration in Microsoft Visual Studio

• Visual Studio .NET 2002* is not supported
• Support the Inherited Project Property Sheet feature of Visual Studio 2005*
• Support the Custom Build Rule feature of Visual Studio 2005
• Improved support for remote debugging of Visual Studio 2005
• Support the automation interfaces of the Intel C++ Project System
• Added a tool bar with three icons in Visual Studio .NET 2003 and Visual Studio 2005. The three icons are: Quick Start Help, Use Intel C++, Use Visual C++
• Support the Project Property Sheet feature
• The command line tool for project conversion is " ICProjConvert100.exe". It's installed under <common files>intel\\shared files\\ia32

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)

void foo(a,b,c)
   int a;
   float b;
   float c[10];
{
   int i = 0;
   for(i=0;i<10;i++)
      c[i]=b*a;
}

• a module-definition (.def) file
• __declspec(dllexport)

The Intel® C++ Compiler for Windows supports both methods.

But please note on how the .def is supported.
The module-definition (.def) file is ONLY used at link time for both Intel C++ compiler and Visual C++. When /Qipo (/GL) is used, the Intel C++ compiler will do more aggressive inlining and optimization. Some functions may be completely inlined so the function body will be removed at compile time if there is no "__declspec(dllexport)" in front of the function.
In such cases if the function name is in the .def file, you will get a link error "xxx.def : error LNK2001: Unresolved external symbol "YYY"".

This is not a bug in the Intel C++ compiler for Windows.

The resolution for this:

• add the "__declspec(dllexport)" in front of the function declaration so the Intel C++ compiler will know at compile time that this function will be used for exporting.

Problem :  gcc and the Intel® C++ Compiler* provide macros that are defined when the -msse (gcc) or -x (Intel) options are used.  The Intel® C++ Compilers 11.0.069 for Linux*,  11.0.054 for Mac OS* and 11.0.061 for Windows* support -xSSE4.1 and -xSSE4.2 options, but do not provide the corresponding __SSE4_1__ and __SSE4_2__ macro definitions.


Environment : Windows*, Linux* or Mac OS* X; C++; IA-32 or Intel® 64 platforms


Root Cause : Already stated above


Resolution : 
These macros are now defined in

• the Intel® C++ Compilers for Linux* 11.0.074 and later
• the Intel® C++ Compilers for Mac OS* 11.0.056 and later
• the Intel® C++ Compilers for Windows* 11.0.066 and later
• the Intel Parallel Composer

IA-32 Architecture refers to systems based on 32-bit processors generally compatible with the Intel Pentium® II processor, (for example, Intel® Pentium® 4 processor or Intel® Xeon® processor), or processors from other manufacturers supporting the same instruction set, running a 32-bit operating system.

Intel® 64 Architecture (formerly Intel® EM64T)refers to systems based on IA-32 architecture processors which have 64-bit architectural extensions, (for example, Intel® Core™2 processor family), running a 64-bit operating system such as Microsoft Windows Vista* x64 or a Linux* "x86_64" variant. If the system is running a 32-bit  operating system, then IA-32 architecture applies instead. Systems based on AMD* processors running a 64-bit operating system are also supported by Intel compilers for Intel® 64 architecture applications.

64-bit computing on Intel architecture requires a computer system with a processor, chipset, BIOS, operating system, device drivers and applications enabled for Intel® 64 architecture. Performance will vary depending on your hardware and software configurations. Consult with your system vendor for more information.

IA-64 Architecture refers to systems based on the Intel® Itanium® processor running a 64-bit operating system.