“Intel C++ Compiler”的意思、由来-开放百科全书

Intel C++ Compiler, also known as icc or icl, is a group of C and C++ compilers from Intel available for Windows, Mac, Linux, FreeBSD^[3] and Intel-based Android devices.

Overview

The compilers generate optimized code for IA-32 and Intel 64 architectures, and non-optimized code for non-Intel but compatible processors, such as certain AMD processors. A specific release of the compiler (11.1) is available for development of Linux-based applications for IA-64 (Itanium 2) processors.

The 14.0 compiler added support for Intel-based Android devices and optimized vectorization and SSE Family instructions for performance. The 13.0 release added support for the Intel Xeon Phi coprocessor. It continues support for automatic vectorization, which can generate SSE, SSE2, SSE3, SSSE3, SSE4, AVX and AVX2 SIMD instructions, and the embedded variant for Intel MMX and MMX 2.^[4] Use of such instruction through the compiler can lead to improved application performance in some applications as run on IA-32 and Intel 64 architectures, compared to applications built with compilers that do not support these instructions.

Intel compilers support Cilk Plus, which is a capability for writing vectorized and parallel code that can be used on IA-32 and Intel 64 processors or which can be offloaded to Xeon Phi coprocessors. They also continue support for OpenMP 4.0, symmetric multiprocessing, automatic parallelization, and Guided Auto-Parallization (GAP). With the add-on Cluster OpenMP capability, the compilers can also automatically generate Message Passing Interface calls for distributed memory multiprocessing from OpenMP directives.

Intel C++ is compatible with Microsoft Visual C++ on Windows and integrates into Microsoft Visual Studio. On Linux and Mac, it is compatible with GNU Compiler Collection (GCC) and the GNU toolchain. Intel C++ Compiler for Android is hosted on Windows, OS X or Linux and is compatible with the Android NDK, including gcc and the Eclipse IDE. Intel compilers are known for the application performance they can enable as measured by benchmarks, such as the SPEC CPU benchmarks.

Optimizations

Intel compilers are optimized to computer systems using processors that support Intel architectures. They are designed to minimize stalls and to produce code that executes in the fewest possible number of cycles. The Intel C++ Compiler supports three separate high-level techniques for optimizing the compiled program: interprocedural optimization (IPO), profile-guided optimization (PGO), and high-level optimizations (HLO). The Intel C++ compiler in the Parallel Studio XE products also supports tools, techniques and language extensions for adding and maintaining application parallelism on IA-32 and Intel 64 processors and enables compiling for Intel Xeon Phi processors and coprocessors.

Profile-guided optimization refers to a mode of optimization where the compiler is able to access data from a sample run of the program across a representative input set. The data would indicate which areas of the program are executed more frequently, and which areas are executed less frequently. All optimizations benefit from profile-guided feedback because they are less reliant on heuristics when making compilation decisions.

High-level optimizations are optimizations performed on a version of the program that more closely represents the source code. This includes loop interchange, loop fusion, loop fission, loop unrolling, data prefetch, and more.^[5]

Interprocedural optimization applies typical compiler optimizations (such as constant propagation) but using a broader scope that may include multiple procedures, multiple files, or the entire program.^[6]

Intel's compiler has been criticized for applying, by default, floating-point optimizations not allowed by the C standard and that require special flags with other compilers such as gcc.^[7]

Architectures

Description of packaging

Except for the Intel Bi-Endian C++ Compiler, Intel C++ compilers are not available in standalone form. They are available in suites:

The suites include other build tools, such as libraries, and tools for threading and performance analysis.

History since 2003

Flags and manuals

Debugging

The Intel compiler provides debugging information that is standard for the common debuggers (DWARF 2 on Linux, similar to gdb, and COFF for Windows). The flags to compile with debugging information are /Zi on Windows and -g on Linux. Debugging is done on Windows using the Visual Studio debugger and, on Linux, using gdb.

While the Intel compiler can generate a gprof compatible profiling output, Intel also provides a kernel level, system-wide statistical profiler called Intel VTune Amplifier. VTune can be used from a command line or thru an included GUI on Linux or Windows. It can also be integrated into Visual Studio on Windows, or Eclipse on Linux). In addition to the VTune profiler, there is Intel Advisor that specializes in vectorization optimization and tools for threading design and prototyping.

Intel also offers a tool for memory and threading error detection called Intel Inspector XE. Regarding memory errors, it helps detect memory leaks, memory corruption, allocation/de-allocation of API mismatches and inconsistent memory API usage. Regarding threading errors, it helps detect data races (both heap and stack), deadlocks and thread and synch API errors.

Reception

Intel and third parties have published benchmark results to substantiate performance leadership claims over other commercial, open-source and AMD compilers and libraries on Intel and non-Intel processors. Intel and AMD have documented flags to use on the Intel compilers to get optimal performance on Intel and AMD processors.^[11]^[12] Nevertheless, the Intel compilers have been known to produce sub-optimal code for processors from vendors other than Intel. For example, Steve Westfield wrote in a 2005 article at the AMD website:^[13]

This vendor-specific CPU dispatching decreases the performance on non-Intel processors of software built with an Intel compiler or an Intel function library – possibly without the knowledge of the programmer. This has allegedly led to misleading benchmarks.^[14] A legal battle between AMD and Intel over this and other issues has been settled in November 2009.^[15] In late 2010, AMD settled a US Federal Trade Commission antitrust investigation against Intel.^[16]

In compliance with this rule, Intel added an "optimization notice" to its compiler descriptions stating that they "may or may not optimize to the same degree for non-Intel microprocessors" and that "certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors". It says that:^[18]

As reported by The Register^[19] in July 2013, Intel was suspected of "benchmarksmanship", when it was shown that the object code produced by the Intel compiler for the AnTuTu Mobile Benchmark omitted portions of the benchmark which showed increased performance compared to ARM platforms.

See also

References

1. ^{{cite web |title= Intel C++ Compiler 19.0 Release Notes|url= https://software.intel.com/en-us/articles/intel-cpp-compiler-release-notes#2019u1}}
2. ^{{cite web |title=Intel C++ Compiler for Android documentation |url=http://software.intel.com/c-compiler-android}}
3. ^{{cite web|url=https://software.intel.com/en-us/articles/intel-system-studio-2016-for-freebsd|title=Intel® System Studio 2016 for FreeBSD* {{!}} Intel® Software|website=software.intel.com|language=en|access-date=2018-03-15}}
4. ^A. J. C. Bik, The Software Vectorization Handbook (Intel Press, Hillsboro, OR, 2004), {{ISBN|0-9743649-2-4}}.
5. ^The Software Optimization Cookbook, High-Performance Recipes for IA-32 Platforms, Richard Gerber, Aart J.C. Bik, Kevin B. Smith, and Xinmin Tian, Intel Press, 2006
6. ^Intel C++ Compiler XE 13.0 User and Reference Guides
7. ^The pitfalls of verifying floating-point computations, by David Monniaux, also printed in ACM Transactions on programming languages and systems (TOPLAS), May 2008; section 4.3.2 discusses nonstandard optimizations.
8. ^This note is attached to the release in which Cilk Plus was introduced. This ULR points to current documentation: http://software.intel.com/en-us/intel-composer-xe/
9. ^Intel C++ Composer XE 2013 Release Notes http://software.intel.com/en-us/articles/intel-c-composer-xe-2013-release-notes/
10. ^{{cite web|url=http://www.intel.com/software/products/compilers/docs/cwin/release_notes.htm |title=Intel® Compilers | Intel® Developer Zone |publisher=Intel.com |date=1999-02-22 |accessdate=2012-10-13}}
11. ^ {{webarchive|url=https://web.archive.org/web/20100323062819/http://software.intel.com/sites/products/documentation/hpc/compilerpro/en-us/cpp/win/compiler_c/index.htm|date=March 23, 2010}}
12. ^{{cite web |url=http://developer.amd.com/Assets/CompilerOptQuickRef-61004100.pdf |title=Archived copy |accessdate=2011-03-30 |deadurl=yes |archiveurl=https://web.archive.org/web/20110322061401/http://developer.amd.com/Assets/CompilerOptQuickRef-61004100.pdf |archivedate=2011-03-22 |df= }}
13. ^{{cite web|url=http://developer.amd.com/documentation/articles/pages/4292005119.aspx|title=Your Processor, Your Compiler, and You: The Case of the Secret CPUID String|publisher=}}
14. ^¹{{cite web|url=http://www.agner.org/optimize/blog/read.php?i=49|title=Agner`s CPU blog - Intel's "cripple AMD" function|website=www.agner.org}}
15. ^{{cite web|url=http://download.intel.com/pressroom/legal/AMD_settlement_agreement.pdf |title=Settlement agreement |website=download.intel.com |format=PDF}}
16. ^{{cite web|url=http://newsroom.intel.com/community/intel_newsroom/blog/2010/08/04/intel-and-us-federal-trade-commission-reach-tentative-settlement |title=Intel and U.S. Federal Trade Commission Reach Tentative Settlement |publisher=Newsroom.intel.com |date=2010-08-04 |accessdate=2012-10-13}}
17. ^FTC, Intel Reach Settlement; Intel Banned From Anticompetitive Practices
18. ^{{cite web|title=Optimization Notice|url=http://software.intel.com/en-us/articles/optimization-notice|publisher=Intel Corporation|accessdate=11 December 2013}}
19. ^{{cite web|url=https://www.theregister.co.uk/2013/07/12/intel_atom_didnt_beat_arm|title=Analyst: Tests showing Intel smartphones beating ARM were rigged|publisher=}}