Install intel c compiler linux

Ubuntu Documentation

Installing the GNU C compiler and GNU C++ compiler

To install the gcc and g++ compilers, you will need the build-essential package. This will also install GNU make.

build-essential contains a list of packages which are essential for building Ubuntu packages including gcc compiler, make and other required tools.

Now, you should able to compile software using C / C++ compilers.

To install the manpages for c and c++ development, install the manpages-dev package.

Installing the GNU Java compiler

Note that GNU’s Java compiler is not the same as the one developed and distributed by Sun Microsystems, and will not provide Java to the firefox browser. For that, please see Java. To install gcj, the GNU Java compiler, install the following package: gcj.

gcj can be used to:

1. compile .java files to bytecode (.class files).
2. compile .java files to a linux-executable.

To install the GNU Java bytecode interpreter, you need the gij package.

To have gcj compile to executables, install libgcj6-dev (otherwise an error during compilation occurs: libgcj.spec: No such file or directory). Use synaptic to install libgcj6-dev.

Installing the GNU Fortran compilers

To install the GNU Fortran 77 compiler — g77, you need the g77 package.

To install the GNU Fortran 95 compiler — gfortran, the package is: gfortran.

Installing the GNU autotools

To install autoconf and automake, you need the autoconf and automake packages.

Apt-get will tell you to explicitly choose a version of automake. If, for example, you decide to use automake1.9, you need to specify the version, such as the automake1.9 package.

32-bit Builds on AMD64

The GNU compilers have options that allow them to create 32-bit object and executable files on 64-bit operating systems, and vica versa. The critical options are -m32 (to build 32-bit) and -m64 (to build 64-bit).

These options will be present when you install the compiler of your choice. However, they won’t actually work unless you install several additional packages.

The first thing you will need is the multilib package for the compiler you are using. For example, to add multilib support to the default version of g++ (4.1 in gutsy), you would install . For 4.2, you would need .

The multilib packages are compiler runtime packages. Now, you need 32-bit (or 64-bit) versions of whatever libraries you need to link your application program. 64-bit packages have names that start with lib64. Install these on 32-bit systems to support 64-bit builds. 32-bit packages have names that start with lib32. Install these on 64-bit systems to support 32-bit builds. Whatever else you are doing, you will probably need . If you are using g++, you will need .

Installing the Intel Compiler Suite Professional Edition 10.x

Using the Intel compilers for C, C++, and FORTRAN requires installing 32-bit libraries for Ubuntu if you are using a 64-bit system. Please ensure you have these packages:

gcc, build-essential, libc6-dev (see above)

ia32-libs, g++-multilib, and libc6-dev-i386 (for 64-bit systems)

32-bit packages starting with lib32 (for 64-bit systems)

alien and rpm for installing the RPM packages that Intel distributes.

libstdc++5 and libstdc++5-3.3-dev for good measure because Intel’s builds depend on these runtimes.

before you attempt installing the Intel Compiler Suite.

Get the License Number and Extract to a path without spaces

Ensure that you have obtained the license number for your installation and extracted the downloaded installation archive into a path that does not contain any spaces. This last statement is utterly important. The installer script that comes with the package has a bug that does not allow you to install the compiler suite if you have any spaces in the installer script path.

On 64-bit systems you may also need to issue these commands

because the chklic_32_64 license checking utility from Intel dynamically links to these libraries.

Once you’re done preparing to install the compiler suite, it’s time to go to the installer directory and install the compiler (be sure to also read through accompanying documentation; e.g., README, INSTALL.txt):

Run the Installation Script

After installing the compiler, you need to tell your shell the location of these executables by adding their parent paths to the PATH environment variable.

Edit /etc/bash.bashrc to add the installation path to the PATH environment variable

Where 10.1.012 is the version of the compiler suite installed.

Installing the X11 development compilers

Install script for X11 development libs

InstallingCompilers (последним исправлял пользователь andrius-zilenas 2012-08-10 10:18:50)

The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details

Источник

Intel® C++ Compiler for Linux* 19.1 Release Notes for Parallel Studio XE 2020

Last Updated: 10/22/2020

Intel® C++ Compiler for Linux* 19.1 Release Notes for Parallel Studio XE 2020

This document provides a summary of new and changed product features and includes notes about features and problems not described in the product documentation.

Please see the licenses included in the distribution as well as the Disclaimer and Legal Information section of these release notes for details. Please see the following links for information on this release of the Intel ® C++ Compiler 19.1.

Change History

Changes in Update 4(New in Intel® C++ Compiler 19.1.3)

• The Intel® Compilers contain functional and security updates
• The Intel® C++ Compiler includes intrinsics for Intel® Advanced Matrix Extensions (Intel® AMX).

Changes in Update 3

• Intel® Parallel Studio XE 2020 Composer Edition for C++ Linux* contains an update to the Intel® C++ Compiler next generation code generator. This is invoked using the -qnextgen option to the ICC and ICPC compilers. This update to the Intel® C++ Compiler next generation code generator includes our latest updates and features for our C++ next generation compiler invoked with the -qnextgen option. There are no new features, bug fixes, or security enhancements for the Intel® C++ Compiler without the -qnextgen option.

Note: Intel® Parallel Studio XE 2020 Update 3 is available for the Intel® Parallel Studio XE 2020 Composer Edition for C++ Linux*.
This is a Linux-only release: there is no Update 3 release for either Windows* or macOS* operating systems.
In addition, it is only a Composer Edition release: there is no Update 3 release for either Professional or Cluster Editions of Intel® Parallel Studio XE 2020.
There is no update to the Intel® C++ Compilers Redistributable Libraries. The Update 2 versions of these libraries are compatible and should be used.
There is no update for the Intel® Parallel Studio XE Runtime 2020 YUM* and APT* repository packages. Continue to use the Update 2 packages of this runtime.

Changes in Update 2 (New in Intel® C++ Compiler 19.1.2)

• Corrections to reported problems

Changes in Update 1 (New in Intel® C++ Compiler 19.1.1)

• Corrections to reported problems.

Changes since Intel® C++ Compiler 19.0 (New in Intel® C++ Compiler 19.1)

System Requirements

• 2GB of RAM (4GB recommended)
• 14GB free disk space for all features
• One of the following Linux distributions (this is the list of distributions tested by Intel; other distributions may or may not work and are not recommended — please refer to Technical Support if you have questions):
  • Debian* 10.0
  • Fedora* 30
  • Red Hat Enterprise Linux* 7,8
  • SUSE LINUX Enterprise Server* 12, 15
  • Ubuntu* 18.04 LTS, 19.04
  • CentOS 8
• Linux Developer tools component installed, including gcc, g++ and related tools
  • gcc versions 4.4 — 9.2 supported
  • minimum gcc versions 5.5 required if using -qnextgen
  • binutils versions 2.20-2.29 supported
• Library libunwind.so is required in order to use the -traceback option. Some Linux distributions may require that it be obtained and installed separately.

Notes

• The Intel compilers are tested with a number of different Linux distributions, with different versions of gcc. Some Linux distributions may contain header files different from those we have tested, which may cause problems. The version of glibc you use must be consistent with the version of gcc in use. For best results, use only the gcc versions as supplied with distributions listed above.
• Compiling very large source files (several thousands of lines) using advanced optimizations such as -O3, -ipo and -openmp, may require substantially larger amounts of RAM.
• Some optimization options have restrictions regarding the processor type on which the application is run. Please see the documentation of these options for more information.

How to use the Intel® C++ Compiler

Parallel Studio XE 2020: Getting Started with the Intel® C++ Compiler 19.1 for Linux* at /documentation_2020/en/compiler_c/ps2020/get_started_lc.htm. contains information on how to use the Intel® C++ Compiler from the command line and from Linux*.

The Intel® C++ Compiler for Linux* does not provide «modulefiles» for usage with the Environmental Modules software utility, but is well suited for such usage. See Using Environment Modules with Intel Development Tools for further information.

Documentation

Product documentation is linked from /documentation_2020/en/compiler_c/ps2020/get_started_lc.htm. Full documentation for all tool components is available at the Intel® Parallel Studio XE Support page.

Offline Core Documentation Removed from the Installed Image

Offline core documentation is removed from the Intel® Parallel Studio XE installed image. The core documentation for the components of Intel® Parallel Studio XE are available at the Intel® Software Documentation Library for viewing online. You can also download an offline version of the documentation from the Intel® Software Development Products Registration Center: Product List > Intel® Parallel Studio XE Documentation.

Please use the instructions from this article to add Intel® Compiler documentation to your local machine.

Japanese Language Support

Intel® compilers optionally provide support for Japanese language users when the combined English-Japanese product is installed. Error messages, visual development environment dialogs and some documentation are provided in Japanese in addition to English. By default, the language of error messages and dialogs matches that of your operating system language selection.

Japanese language support is provided with update 1 of the product.

Intel-provided debug solutions

• Intel®-provided debug solutions are based GNU* GDB. Please see Intel® Parallel Studio XE 2020 Composer Edition C++ — Debug Solutions Release Notesfor further information.

Samples

Product samples are now available online at Intel® Software Product Samples and Tutorials

Technical Support

If you did not register your compiler during installation, please do so at the Intel® Software Development Products Registration Center at http://registrationcenter.intel.com. 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, User Forums, FAQs, tips and tricks, and other support information, please visit: http://www.intel.com/software/products/support/
Note: If your distributor provides technical support for this product, please contact them for support rather than Intel.

New and Changed Features

The following features are new or significantly enhanced in this version. For more information on these features, please refer to the documentation.

This option is supported in versions 19.0 update 8 of the compiler and above. The details about this option can be found in the Intel® C++ Compiler 19.1 Developer Guide and Reference here.

The new -qnextgen compiler option invokes the Intel ® C++ Compiler next generation code generator. These options are only available for Windows* or Linux* ICC/ICL/ICPC drivers. This option and functionality is not available for Intel ® C++ Compiler for macOS* X.

The Intel® C++ Compiler 19.1 supports the following features under the /Qstd=c++20 (Windows*) or -std=c++20 (Linux*/OS X*) options:

• std::is_constant_evaluated and __builtin_is_constant_evaluated

• IF clause on SIMD directive
• NONTEMPORAL clause on SIMD directive

Parallel STL for parallel and vector execution of the C++ STL

Intel(R) C++ Compiler is installed with Parallel STL, an implementation of the C++ standard library algorithms with support for execution policies.

Features/APi changes

• More algorithms support parallel and vector execution policies: find_first_of, is_heap, is_heap_until, replace, replace_if.
• More algorithms support vector execution policies: remove, remove_if.
• More algorithms support parallel execution policies: partial_sort.

To learn more, please refer to article https://software.intel.com/en-us/get-started-with-pstl

Support Deprecated

none at this time

Support Removed

The following compiler options related to Loop Profiler are deprecated and will be removed in future compilers

• profile-loops=keyword
• profile-loops-report=value
• profile-functions
• guide-profile

Intel® Cilk™ Plus support is removed in 19.1
This includes the «#pragma simd» directive. Users should replace with the OpenMP SIMD pragma «#pragma omp simd» and it’s clauses. Remember to add compiler option «-qopenmp-simd» or «-qopenmp». This pragma will be removed in future releases.

Known Limitations

libtinfo.so.5 missing:icc -qnextgen may report missing dependency on the latest versions of Fedora (29+), Ubuntu (18.10+) and SLES15

clang: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

Installing the library will resolve the issue. If the library installed into non-standard location, the location should be added to LD_LIBRARY_PATH.
To install this library, you can add the following packages:Fedora 29+, CentOS, RHEL variants fix:
sudo yum install ncurses-compat-libs-6.1 Ubuntu 18.10+, Debian variants:sudo apt-get install libtinfo5

Parallel STL

unseq and par_unseq policies only have effect with compilers that support ‘#pragma omp simd’ or ‘#pragma simd. Parallel and vector execution is only supported for a subset of algorithms if random access iterators are provided, while for the rest execution will remain serial. Depending on a compiler, zip_iterator may not work with unseq and par_unseq policies.

Pointer Checker requires a dynamic runtime library

When using the -check-pointers option, the runtime library libchkp.so must be linked in. When using options like -static or -static-intel with -check-pointers, be aware that this dynamic library will be linked in regardless of your settings. See the article at Pointer Checker in ICC for more information.

Disclaimer and Legal Information

Intel’s compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804

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 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:

The Intel® C++ Compiler is provided under Intel’s End User License Agreement (EULA).

Please consult the licenses included in the distribution for details.

Intel, Intel logo, Pentium, Core, Atom, Iris, Intel® Xeon®, Intel® Xeon Phi 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 © 2019 Intel Corporation. All Rights Reserved.

Источник