Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 1 Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes Document number: 321414-003US 4 August 2011 Table of Contents 1 Introduction ......................................................................................................................... 3 1.1 Change History ............................................................................................................ 3 1.2 Product Contents ......................................................................................................... 5 1.3 System Requirements.................................................................................................. 5 1.3.1 IA-64 Architecture (Intel® Itanium®) Development Not Supported ........................ 6 1.3.2 Windows Server 2003* and Windows Vista* Support Deprecated......................... 6 1.3.3 Visual Studio 2005* Support Deprecated .............................................................. 6 1.4 Documentation............................................................................................................. 7 1.5 Samples....................................................................................................................... 8 1.6 Japanese Language Support ....................................................................................... 8 1.7 Technical Support ........................................................................................................ 8 2 Installation........................................................................................................................... 8 2.1 Pre-installation Steps ................................................................................................... 8 2.1.1 Configure Visual Studio for 64-bit Applications...................................................... 8 2.1.2 Installation on Microsoft Windows Vista* and Windows 7* .................................... 9 2.2 Installation ................................................................................................................... 9 2.2.1 Using a License or Serial Number from Intel® C++ Compiler 11.1 Professional Edition to Install................................................................................................................... 9 2.2.2 Silent Install .........................................................................................................10 2.2.3 Cluster Installation ...............................................................................................10 2.2.4 Activation of Purchase after Evaluation Using the Intel Activation Tool ................10 2.2.5 Using a License Server ........................................................................................10 2.2.6 Prompt for Administrator Permission with Microsoft Visual Studio 2005* .............10 2.3 Changing, Updating and Removing the Product .........................................................11
31
Embed
Intel® C++ Composer XE 2011 for Windows* Installation ...registrationcenter-download.intel.com/akdlm/irc_nas/2309/w_ccompxe... · Intel® C++ Composer XE 2011 for Windows* Installation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 1
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes
Document number: 321414-003US
4 August 2011
Table of Contents 1 Introduction ......................................................................................................................... 3
1.1 Change History ............................................................................................................ 3
If Microsoft Cluster Compute Pack* is present, and the installation detects that the installing
system is a member of a cluster, the product will be installed on all visible nodes of the cluster
when a ―Full‖ installation is requested. If a ―Custom‖ installation is requested, you will be given
the option to install on the current node only.
2.2.4 Activation of Purchase after Evaluation Using the Intel Activation Tool
Note for evaluation customers a new tool Intel Activation Tool ―ActivationTool.exe‖ is included in
this product release and installed at ―[Common Files]\Intel\Parallel Studio XE
2011\Activation\‖.
If you installed the product using an Evaluation license or SN, or using the ―Evaluate this
product (no serial number required)‖ option during installation, and then purchased the product,
you can activate your purchase using the Intel Activation Tool at Start > All Programs > Intel
Parallel Studio XE 2011 > Product Activation. It will convert your evaluation software to a fully
licensed product.
2.2.5 Using a License Server
If you have purchased a ―floating‖ license, see http://software.intel.com/en-us/articles/licensing-setting-up-the-client-floating-license/ for information on how to install using a license file or license server. This article also provides a source for the Intel® License Server that can be installed on any of a wide variety of systems.
2.2.6 Prompt for Administrator Permission with Microsoft Visual Studio 2005*
If you are installing on Microsoft Windows Vista* or later versions of Microsoft Windows and are using Microsoft Visual Studio 2005, Windows may display a dialog similar to the following:
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 11
If this is displayed, it is important that you click the Continue button and leave the ―Always show this message‖ box checked. If you select ―Exit Visual Studio‖ instead, or do nothing (this message times out after two minutes), the compiler integration will not install completely. For more information, see Installation on Microsoft Windows Vista*.
2.3 Changing, Updating and Removing the Product
Use the Windows Control Panel ―Add or Remove Products‖ applet to change which product
components are installed or to remove the product.
When installing an updated version of the product, you do not need to remove the older version
first. You can have multiple versions of the compiler installed and select among them. If you
remove a newer version of the product you may have to reinstall the integrations into Microsoft
Visual Studio from the older version.
2.4 Installation Folders
The installation folder arrangement is shown in the diagram below. Not all folders will be present
in a given installation.
C:\Program Files\Intel\Composer XE 2011 SP1
o bin
ia32
ia32_intel64
intel64
o compiler
include
ia32
intel64
lib
ia32
intel64
o debugger
o Documentation
o Help
o ipp
bin
demo
include
interfaces
lib
tools
o mkl
benchmarks
bin
examples
include
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 12
interfaces
lib
tests
tools
o tbb
bin
examples
include
lib
o redist
o Samples
o VS Integration
Where the folders under bin, include and lib are used as follows:
ia32: Files used to build applications that run on IA-32
intel64: Files used to build applications that run on Intel® 64
ia32_intel64: Compilers that run on IA-32 to build applications that run on Intel®64
If you are installing on a system with a non-English language version of Windows, the name of
the Program Files folder may be different. On Intel® 64 architecture systems, the folder
name is Program Files (X86) or the equivalent.
By default, updates of a given version will replace the existing directory contents. When the first
update is installed, the user is given the option of having the new update installed alongside the
previous installation, keeping both on the system. If this is done, the top-level folder name for
the older update is changed to Composer XE 2011 SP1.nnn where nnn is the update
number.
2.5 Installation Known Issues
2.5.1 Documentation Issue with Multiple Visual Studio Versions
If you have both Microsoft Visual Studio* 2005 and 2008 installed on your system and integrate
Intel® C++ Composer XE 2011 into both versions, removing the integration from one of the
versions will remove the integrated Intel® C++ Composer XE 2011 documentation from both.
To re-install the documentation:
1. Use the Control Panel to select the product.
For Windows XP* users: Select Control Panel > Add/Remove Programs.
For Windows 7* users: Select Control Panel > Programs and Features.
For Windows Vista* users: Select Control Panel > Programs.
2. With the product selected, click the Change/Remove button and choose Modify mode.
3. In the Select Components dialog box, unselect ―Integrated Documentation;‖ this will
remove the documentation.
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 13
4. Repeat steps 1 and 2.
5. In the Select Components dialog box, select ―Integrated Documentation‖ to install
documentation again
3 Intel® C++ Compiler This section summarizes changes, new features and late-breaking news about the Intel C++
Compiler.
3.1 Compatibility
In version 11, the IA-32 architecture default for code generation has changed to assume that
Intel® Streaming SIMD Extensions 2 (Intel® SSE2) instructions are supported by the processor
on which the application is run. See below for more information.
3.2 New and Changed Features
C++ Composer XE 2011 Update 6 now contains Intel® C++ Compiler XE 12.1. The following
features are new or significantly enhanced in this version. For more information on these
features, please refer to the documentation viewable from within Visual Studio.
Features from C++0x
o Variadic templates
o char16_t and char32_t data types
o _Pragma
o Function deletion
o Member function default
o sizeof, typeid or decltype can refer directly to a non-static data member of a class
o nullptr
o Attributes with double square brackets
o alias and alias template declarations
o New function declaratory syntax with return type (i.e. auto f()->int;)
OpenMP* 3.1
o final clause
o mergeable clause
o taskyield directive
o new atomic clauses
Improved IDE integration for Static Security Analysis
Improvements to Intel® Cilk™ Plus, including
o New holder hyperobject
The following features are new or significantly enhanced in Intel® C++ Compiler XE 12.0. For
more information on these features, please refer to the documentation viewable from within
Visual Studio.
Intel® Cilk™ Plus language extensions for the Intel® C++ Compiler make it easy to add
parallelism to both new and existing software.
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 14
Guided Auto-Parallelism
Features from C++0x
o rvalue references
o Standard atomics
o Support of C99 hexadecimal floating point constants when in ―Windows C++‖
mode
o Right angle brackets
o Extended friend declarations
o Mixed string literal concatenations
o Support for long long
o Variadic macros
o Static assertions
o Auto-typed variables
o Extern templates
o __func__ predefined identifier
o Declared type of an expression (decltype)
o Universal character name literals
o Strongly-typed enums
o Lambdas
An option to use math library functions that are faster but return results with less
precision or accuracy
An option to use math library functions that return consistent results across different
models and manufacturers of processors
3.2.1 Intel® Cilk™ Plus Array Notations Semantics Change in update 6
In Intel® C++ Composer XE 2011, a Cilk Plus array section assignment like the following:
a[:] = b[:] + c[:];
could potentially generate temporary copies of the results, impacting performance.
Starting in Intel® C++ Composer XE 2011 update 6, if an array section on the right hand side of
an assignment (in the example given, b[:] or c[:]) partially overlaps the array section on the left
hand side (in the example given, a[:]) in memory, this assignment will be undefined, and it is up
to the programmer to assure that there is no partial overlap in memory on assignments in order
to get defined behavior.
An exception to this is if the array sections completely overlap, for example:
a[:] = a[:] + 3;
Since array a overlaps itself completely, this summation will work as expected.
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 15
3.2.2 Intel® Cilk™ Plus “scalar” Clause Deprecated
The ―scalar‖ clause used optionally with Cilk Plus elemental functions is being deprecated and
will be removed in a future version of C++ Composer XE. Please use the functionally equivalent
―uniform‖ clause instead.
3.2.3 Additional Keywords for /Qsox option, default changed in update 3
The /Qsox option, which adds information to the object file about compiler options used and
procedure profiling information, has been enhanced to let the user request that the list of inlined
functions be included and to let the user exclude information about procedure profiling.
The syntax for /Qsox is now:
/Qsox[-]
/Qsox=keyword[,keyword]
Where keyword is one of inline or profile. If /Qsox is specified with no keywords, only
the command line options are included – this is a change from previous releases. To maintain
the previous behavior, use /Qsox=profile. Multiple /Qsox options may be specified on the
command line – if so, they are interpreted in left-to-right order.
The information is added to the object file as comment directives. These are ignored by
Microsoft linkers beginning with Visual Studio 2005, therefore the information will not be present
in the executable.
3.2.4 Three intrinsics changed in update 2
Three intrinsics (_rdrand16_step(), _rdrand32_step(), _rdrand64_step()) have been changed in
update 2. The documentation has not been updated with these new changes. These intrinsic
return a hardware-generated random value and are declared in the ―immintrin.h‖ header file.
These three intrinsics are mapped to a single RDRAND instruction, generate random numbers
of 16/32/64 bit wide random integers.
Syntax
1. extern int _rdrand16_step(unsigned short *random_val);
2. extern int _rdrand32_step(unsigned int *random_val);
3. extern int _rdrand64_step(unsigned __int64 *random_val);
Description
The intrinsics perform one attempt to generate a hardware generated random value
using the instruction RDRAND. The generated random value is written to the given
memory location and the success status is returned: 1 if the hardware returned a valid
random value and 0 otherwise.
Return
A hardware-generated 16/32/64 random value.
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 16
Constraints
The _rdrand64_step() intrinsic can be used only on systems with the 64-bit registers
Another method is to uninstall the Intel C++ Composer XE 2011 and reinstall the Intel C++
Composer XE 2011.
3.5.3 Intel® Cilk™ Plus Known Issues
Microsoft C++ Structured Exception Handling (SEH) will fail if an SEH exception is thrown
after a steal occurs and before the corresponding _Cilk_sync.
3.5.4 Guided Auto-Parallel Known Issues
Guided Auto Parallel (GAP) analysis for single file, function name or specific range of source
code does not work when Whole Program Interprocedural Optimization (/Qipo) is enabled. The
workaround is to disable /Qipo – in Visual Studio, this is Project > [projectname]
Properties > C++ > Optimization > Interprocedural Optimization > No.
3.5.5 Static Security Analysis Known Issues
3.5.5.1 Excessive false messages on C++ classes with virtual functions
Note that use of the Static Security Analysis feature also requires the use of Intel® Inspector
XE.
Static security analysis reports a very large number of incorrect diagnostics when processing any program that contains a C++ class with virtual functions. In some cases the number of spurious diagnostics is so large that the result file becomes unusable. If your application contains this common C++ source construct, add the following command line
switch to suppress the undesired messages:/Qdiag-disable:12020,12040 (Windows) or –
diag-disable 12020,12040 (Linux). This switch must be added at the link step
because that is when static security analysis results are created. Adding the switch at the compile step alone is not sufficient. In Microsoft Visual Studio, add this to the property page Linker > Command Line.
If you are using a build specification to perform static security analysis, add the –disable-id
12020,12040 switch to the invocation of the inspxe-runsc, for example, inspxe-runsc –spec-file mybuildspec.spec -disable-id 12020,12040
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 22
If you have already created a static security analysis result that was affected by this issue and you are able to open that result in the Intel® Parallel Inspector XE GUI, then you can hide the undesired messages as follows:
The messages you will want to suppress are “Arg count mismatch” and “Arg type
mismatch”. For each problem type, do the following:
Click on the undesired problem type in the Problem filter. This hides all other problem types.
Click on any problem in the table of problem sets
Type control-A to select all the problems
Right click and select Change State -> Not a problem from the pop-up menu to set the state of all the undesired problems
Reset the filter on problem type to All
Repeat for the other unwanted problem type
Set the Investigated/Not investigated filter to Not investigated. You may have to scroll down in the filter pane to see it as it is near the bottom. This hides all the undesired messages because the ―Not a problem‖ state is considered a ―not investigated‖ state.
4 Intel® Integrated Performance Primitives This section summarizes changes, new features and late-breaking news about this version of
Intel® Integrated Performance Primitives (Intel® IPP). For detailed information about IPP see
the following links:
New features: see the information below and visit the main Intel IPP product page on
the Intel web site at: http://www.intel.com/software/products/ipp; and the Intel IPP
Release Notes at http://software.intel.com/en-us/articles/intel-ipp-70-library-release-
notes/.
Documentation, help, and samples: see the documentation links on the IPP product
Disabling the Intel Debugging exceptions during a debug session may cause Visual Studio (up to Visual Studio 2008, SP1) to hang.
Use of the Intel Parallel Debugger Extension requires that the OpenMP library be linked dynamically, which is the default. If you wish to use the Parallel Debugger Extension, do
not use /Qopenmp-link:static to specify static linking of the OpenMP Library.
Be sure to enable the parallel debug instrumentation (switch /debug:parallel) before you
(/debug:parallel). Otherwise, the debugger will not detect data sharing events nor
break on re-entrant calls.
Microsoft Visual Studio 2010 users: If you have specified that the project be built with Microsoft Visual C++, and then change the project to use the Intel C++ compiler, you
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 30
must close and re-open the solution for the Parallel Debug Environment property setting ―Auto‖ to be recognized.
If you are using Microsoft Visual Studio 2008 and debugging 64-bit applications, you must have Visual Studio 2008 Service Pack 1 installed.
o You can debug 64-bit applications under Visual Studio 2005 and 2008 without Service Packs only if they are linked to the low memory area. If not linked to the low memory area, you will not see any events until the debuggee terminates. After termination, all events are displayed in the event window. In order to debug
64-bit applications properly, set the base address to 0x10000 in Project >
Properties > Linker > Advanced.
Function local or heap variables are displayed as ―???‖ in the data sharing event window.
The SSE Registers window does not work for 64-bit applications - the window shows
"???"
Filters on static local variables are not set correctly via context menu.
Reentrant call detection stops in Disassembly view. It does not work correctly for static functions. When used in design mode, the function should be preceded by a suitable
context operator, for example, {,,myapp.exe} my_extern_function
The debugger extension windows remain empty when their placement is changed from "docked" to "floating". The workaround is to either keep them docked or to restart the debug session after the placement was changed.
The debugger extension requires the application to be started from Visual Studio. It does not work when attaching to an existing process.
Windows settings are restored to default (Hexadecimal) when the window is hidden or closed and reopened again.
7.4 Documentation
Intel Parallel Debugger Extension Documentation can be accessed via the Help menu of
Microsoft Visual Studio or by pressing the function key F1 after activation of a Parallel Debugger
Extension window. Help is also available by clicking the link ―HTML version‖ inside debugger-
documentation.htm.
8 Disclaimer and Legal Information INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL(R)
PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO
ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS
PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL
ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR
Intel® C++ Composer XE 2011 for Windows* Installation Guide and Release Notes 31
IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS
INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR
PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR
OTHER INTELLECTUAL PROPERTY RIGHT. UNLESS OTHERWISE AGREED IN WRITING
BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY
APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A
SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.
Intel may make changes to specifications and product descriptions at any time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked
"reserved" or "undefined." Intel reserves these for future definition and shall have no
responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
The information here is subject to change without notice. Do not finalize a design with this
information.
The products described in this document may contain design defects or errors known as errata
which may cause the product to deviate from published specifications. Current characterized
errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and
before placing your product order.
Copies of documents which have an order number and are referenced in this document, or
other Intel literature, may be obtained by calling 1-800-548-4725, or go to:
http://www.intel.com/design/literature.htm
Intel processor numbers are not a measure of performance. Processor numbers differentiate
features within each processor family, not across different processor families. Go to: