This product is available in two editions.
The Standard Edition contains the following components:
<install-dir>/doc/Doc_Index.html
The Professional Edition includes all of the Standard Edition and adds:
These additional components of the Professional Edition are installed separately and have their own Release Notes.
Note: The installation path for the Intel® C++
Compiler is /opt/intel/cc/10.1.xxx (32-bit) or /opt/intel/cce/10.1.xxx (64-bit),
where xxx represents
a 3-digit update number. The term <install-dir> is
used in throughout this document to refer to the default installation
path.
To receive technical support and product updates for the tools provided in this product you need to register. For how to register, please see Technical Support section below.
The following section discusses new features and changes in the Intel C++ Compiler since version 10.0. Please see the separate release notes for the Intel Debugger.
The following is a listing of command line options that are new or have changed since the version 9.1 release. Please refer to the compiler documentation for more information on these options.
-alias-const[-]-[no-]check-uninit-cxxlib-nostd-diag-<type> <diag-list>-diag-dump-diag-enable port-win -diag-enable sv[1|2|3] -diag-enable sv-include-diag-file[=file] -diag-file-append[=file]-[no-]diag-id-numbers -dumpmachine-f[no-]align-functions[=n]-fast-fargument-noalias-global-f[no-]exceptions-f[no-]instrument-functions-f[no-]jump-tables -f[no]-keep-static-consts-fmudflap-fp-speculation=<mode>-gcc-sys-help [category]-[no-]inline-calloc calloc() as
calls to malloc() and memset(). (Default:
off) -ipo-jobs<n>-m32-m64-msse3 -nostdinc++-[no-]opt-class-analysis-opt-malloc-options=n malloc().
(Default: 0) -[no-]opt-multi-version-aggressive-opt-ra-region-strategy [=keyword]default) -opt-streaming-stores keywordauto) -[no-]par-runtime-control-par-schedule-<keyword>[[]n]-save-temps[-]-shared-intellibguide)-static-intellibguide)-tcheck [<mode>]-trigraphs-[no-]unroll-aggressive-[no-]vec-guard-write-Weffc++-W[no-]missing-declarations-Wnon-virtual-dtor-Wreorder -W[no-]strict-prototypes-Wunused-variable-Wwrite-stringsconst char * is
converted to (non-const) char *. (Default: off)For information on command line options that are either deprecated (still functional but to be removed in a future version) or removed (no longer supported), please refer to the section Compiler Options > Deprecated and Removed Compiler Options in the on-disk documentation.
-fast Changed The -fast option is a shorter way of specifying a set of options
that generally improve run-time performance. As documented, the
set of options may change over time. In version 10.0, -fast sets -xT,
whereas in earlier versions it set -xP. If this change is not
appropriate for you, you must specify the individual options you
want instead of using -fast. Please see the Compiler Options
section of the on-disk documentation for further information.
Many command line options have an older spelling where underscores (“_”) instead of hyphens (“-“) connect the words in the option name. The older spelling is still a valid alternate option name.
This version includes two compilers, one that generates code for Mac* systems based on Intel® 64 architecture processors, and one that generates code for Mac* systems based on IA-32 architecture processors.
This version features a complete new design of exception handling with simpler internal presentation to provide more opportunities for optimization. Improvements include:
"Mudflap" is a pointer user checking technology based on compile-time instrumentation. It adds protective code to a variety of potentially unsafe C/C++ constructs that detect actual erroneous uses at run time. The class of errors detected includes:
C++ Class Hierarchy Analysis uses C++ class hierarchy information to provide information to the compiler so that it can resolve more virtual function targets at compile time thus improving performance.
The cpu_dispatch and cpu_specific keywords now
accept the cpuid code core_2_duo_ssse3 for Intel® Core™2
processors and Intel® Xeon® processors with Supplemental Streaming
SIMD Extensions 3 (SSSE3).
This version features a complete redesign of the optimizer that integrates
parallelization and vectorization at O2 and O3 optimization levels
with memory and loop optimizations.
Performance can be substantially improved by:
Loop Transformation (HLO) Optimization reports tell you why the compiler was unable to apply loop interchange transformations on a set of loops and suggests loop interchange if the reported bottlenecks can be removed by source changes. These reports have been enhanced to provide more detailed information and to be easier to understand.
new Expression with Parenthesized
TypeIn a new expression, a parenthesized type followed
immediately by an array index is not valid C++. For example:
int main()
{
char *p1 = new (char *)[20]; // array index is not allowed after ")"
return 0;
}
In previous versions, the Intel C++ compiler would accept this code and either interpret it as if the array index was part of the type being created:
new ((char*)[20])
or not:
(new (char *))[20]
depending upon the reference compiler and compatibility version target. The compiler has now been changed to always give an error for this incorrect usage.
-std=c99 and -std=c89 When the -std=c99 or -std=c89 options
are used, the 10.1 compiler's behavior is now compatible with gcc
and the __STRICT_ANSI__ macro is predefined. If your
application compiles with errors and you wish to use the previous
version's behavior, add -U__STRICT_ANSI__ to the command
line.
Static Verifier is a new compiler feature which performs static
analysis of a program across multiple source files. It can detect
different kinds of defects and doubtful or inconsistent uses of
language features in user code and report them according to their
severity level. Static Verifier understands C/C++ and Fortran code
and can also perform analysis of OpenMP directives.
In this release, when Static Verifier is enabled the linker is not invoked so
an executable or static/dynamic link library is not produced, object files that
were produced as a result of invocation of Static Verifier are not valid and
should not be used for generating of real executable or static/dynamic link libraries.
The current usage model is that Static Verifier is added as an alternate build
option to produce a diagnostic report.
For more information, please refer to the section on Building Applications > Error Handling > Handling Compile Time Errors > using Static Verification Diagnostic Options in the on-disk documentation.
When Static Verifier support is enabled within the IDE, the customary final build target (e.g. an executable image) is not created. As such, we recommend that a separate "Static Verification" configuration be created, by cloning the existing Debug (development) configuration, for use when static verification is desired.
-ansi no longer implies -fp-port In previous versions of the compiler, the -ansi switch
implied -fp-port. In version 10.1, -ansi no longer implies -fp-port. As a result, the compiler generates
more efficient floating-point code under -ansi, especially when
using x87 instructions to implement FP calculations. Use -fp-port in addition to -ansi if it is important to round FP data to source
precision at assignments and casts.
In version 9.1, the compiler inserted an underscore at the beginning of function names created through asm declarations. While this matched the behavior of gcc on Linux*, it did not match the gcc behavior on Mac OS. In version 10.1, the extra underscore is no longer generated.
Notes:
Please see the separate Installation Guide for information on installing the compiler and setting up the compiler environment.
.o files must be saved for debuggingStarting with Xcode 2.3, the Dwarf debugging information is stored in the
object (.o) files. These object files are accessed by debuggers to obtain
information related to the application being debugged and thus must be available
for symbolic debugging.
In cases where a program is compiled and linked in one command, such as:
icc -g -o hello.exe hello.c
the object files are generated by the compiler but deleted before the command completes.
To make such an application debuggable, use the compiler
switch -save-temps to direct the compiler to keep the .o files,
for example:
icc
-g -save-temps -o hello.exe hello.c
This switch is not necessary
when the application is built in two steps with explicit production
of a .o file, for example:
icc -c -g -o hello.o hello.c
icc -g -o hello.exe hello.o
When linking an application compiled with the Intel compiler, you may receive
numerous warnings from ld of the form:
ld: warning suggest use of -bind_at_load, as lazy binding may result in
errors or different symbols being used
symbol _fdim used from dynamic
library /usr/lib/system/libmathCommon.A.dylib(single module) not from
earlier dynamic library libimf.dylib(fdim_stub.o)
[…]
This warning occurs for 16 symbols found in both libimf.dylib and libmathCommon.A.dyblib.
It happens only in the case where Intel libraries are linked dynamically
(the default); linking Intel libraries statically will not yield these
warnings. In cases we have evaluated, the symbols in question were
properly linked from libimf.dylib in the executable or dynamic
library being linked. These warning messages can be ignored.
You can use "otool -vH <executable>" to verify
which dynamic libraries the symbols are resolved from.
Library not loaded error when running applicationWhen running an application built with the Intel compiler, you may see an error of the form:
dyld:Library not loaded:libsvml.dylib
reason: image not found
This error occurs when the Intel dynamic libraries cannot be located. To resolve this, follow these steps:
Groups & files pane expand Executables. Info, and navigate to the Arguments dialog box. DYLD_LIBRARY_PATH environment variable
to include the path /opt/intel/cc/10.1.xxx/lib If you did not register your compiler during installation, please do so at the Intel® Software Development Products Registration Center. Registration entitles you to free technical support, product updates and upgrades for the duration of the support term.
For information about how to find Technical Support, Product Updates, Users Forums, FAQs, tips and tricks, and other support information, please visit: http://www.intel.com/software/products/support/cmac.
Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.
Go" button next to the "Product"
drop-down list.
Submit Issue" link in the left navigation bar.
Development Environment (tools,SDV,EAP)" from the "Product
Type" drop-down list.
Intel(R)
C++ Compiler,
Mac OS* X" from the "Product Name"
drop-down list.
Note: Please notify your support representative prior to submitting source code where access needs to be restricted to certain countries to determine if this request can be accommodated.
Get the Intel C++ Compiler's Package ID with the following commands:
> icc -V
and copy the "Package ID" (e.g. m_cc_x_10.1.xxx)
from the output into the corresponding Intel® Premier
Support field. Please include any other specific information
that may be relevant to helping us to reproduce and address
your concern.
<package ID>_README (e.g. m_cc_x_10.1.xxx_README),
available for download from Intel® Software Development Products Registration Center Product Downloads, to see which issues have been resolved in the
latest version of the compiler.
Compiler Error Source Reducer (CESR) is a set of utilities which are useful individually or collectively in gathering, reducing, pinpointing, protecting, documenting, and bundling test cases comprised of C/C++ or Fortran source code. It can be helpful if you have a large application for which you want to extract a small test case for submission to Intel® Premier Support. CESR can be downloaded from Intel® Software Development Products Registration Center Product Downloads. Select your product and in the version dropdown, select CESR. CESR is unsupported and should be considered experimental, but we welcome your feedback on it through Intel® Premier Support. CESR requires prior installation of Python* 2.2 or newer.
The Intel® C++ Compiler includes extensive user’s guide and reference documentation. You can view the list of available documentation by locating and opening the file alias in the <install-dir> folder; the file alias is Intel(R) C++ Compiler Documentation. (The alias target file is <install-dir>/doc/Doc_Index.html.)
You can gain a quick understanding of compiler operation by executing the procedures in the Getting Started with the Intel(R) C++ Compiler 10.1 for Mac OS* X document. You can view the getting started information by locating and opening the file alias in the <install-dir> folder; the file alias is Getting Started with the Intel(R) C++ Compiler. (The alias target file is <install-dir>/doc/Getting_Started.html.)
Information on Intel software development products is available at http://www.intel.com/software/products.
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 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 by visiting Intel's Web Site.
Celeron, Centrino, Intel, Intel logo, Intel386, Intel486, Intel Core, Itanium, MMX, Pentium, VTune, and Xeon are trademarks of Intel Corporation in the U.S. and other countries.
* Other names and brands may be claimed as the property of others.
Copyright (C) 2007, Intel Corporation. All Rights Reserved.