{{Note|Packages that have been compiled by icc will depend on the associated libs contained in the '''intel-openmp''' package in order to run. Since '''intel-openmp''' depends on '''intel-compiler-base''', users MUST have both packages installed at all times!}}

{{Note|Packages that have been compiled by icc will depend on the associated libs contained in the '''intel-openmp''' package in order to run. Since '''intel-openmp''' depends on '''intel-compiler-base''', users MUST have both packages installed at all times!}}

−

==Setup and Installation==

+

== Setup and installation ==

+

{{AUR|intel-parallel-studio-xe}} are available in the [[AUR]]. To build the package, one needs a license file which is free for personal and for non-commercial use. The requisite license file is emailed to users upon [[https://registrationcenter.intel.com/RegCenter/AutoGen.aspx?ProductID=1517&AccountID=&EmailID=&ProgramID=&RequestDt=&rm=NCOM&lang= registration]] and should be copied into the $startdir prior to running makepkg. The current PKGBUILD assembles 7 or 8 packages:

{{AUR|intel-parallel-studio-xe}} are available in the [[AUR]]. To build the package, one needs a license file which is free for personal and for non-commercial use. The requisite license file is emailed to users upon [[https://registrationcenter.intel.com/RegCenter/AutoGen.aspx?ProductID=1517&AccountID=&EmailID=&ProgramID=&RequestDt=&rm=NCOM&lang= registration]] and should be copied into the $startdir prior to running makepkg. The current PKGBUILD assembles 7 or 8 packages:

{{Note|A minimal working environment requires the '''intel-compiler-base''' and '''intel-openmp''' packages; if you want also the fortran compiler you must install '''intel-fortran-compiler'''.}}

{{Note|A minimal working environment requires the '''intel-compiler-base''' and '''intel-openmp''' packages; if you want also the fortran compiler you must install '''intel-fortran-compiler'''.}}

−

==Using icc with makepkg==

+

== Using icc with makepkg ==

+

{{Note|Not every package will successfully compile with icc without heavy modifications to the underlying source.}}

{{Note|Not every package will successfully compile with icc without heavy modifications to the underlying source.}}

There is currently no official guide to using icc with makepkg. This section is meant to capture various methods suggested by users. Please make a new sub-section with your suggested method titled as such.

There is currently no official guide to using icc with makepkg. This section is meant to capture various methods suggested by users. Please make a new sub-section with your suggested method titled as such.

−

=== Method 1 ===

+

=== Method 1 (12/08/2012) ===

+

Modify {{ic|/etc/makepkg.conf}} inserting the following code ''under'' the existing line defining '''CXXFLAGS''' to enable makepkg to use icc. No special switches are needed when calling makepkg to build.

Modify {{ic|/etc/makepkg.conf}} inserting the following code ''under'' the existing line defining '''CXXFLAGS''' to enable makepkg to use icc. No special switches are needed when calling makepkg to build.

{{bc|1=_CC=icc

{{bc|1=_CC=icc

if [ $_CC = "icc" ]; then

if [ $_CC = "icc" ]; then

−

export CFLAGS="-fast -pipe -gcc"

+

export CC="icc"

−

export CXXFLAGS="${CFLAGS}"

+

export CXX="icpc"

−

export CC="icc"

+

export CFLAGS="-march=native -O3 -no-prec-div -fno-alias -pipe"

−

export CXX="icpc"

+

export CXXFLAGS="${CFLAGS}"

−

export HOSTCC="icc"

+

export LDFLAGS="-Wl,-O1,--sort-common,--as-needed"

+

export AR="xiar"

+

export LD="xild"

fi}}

fi}}

−

{{Note|To toggle between the native gcc and icc, simple comment or uncomment the newly created '''_CC''' variable.}}

+

{{Note|

−

+

* To toggle between the native gcc and icc, simple comment or uncomment the newly created '''_CC''' variable.

−

{{Note|Is some case the compilation method described above fails and the compilation will be performed with ''gcc'', so you should test if yours application has been effectively compiled with ''icc'' }}

+

* In some case the compilation method described above fails and the compilation will be performed with ''gcc'', so you should test if yours application has been effectively compiled with ''icc''.}}

To test if your package has been really compiled with icc:

To test if your package has been really compiled with icc:

Line 56:

Line 62:

* The last method is to watch if the warnings are in ''icc'' style or not.

* The last method is to watch if the warnings are in ''icc'' style or not.

−

==icc CFLAGS==

+

== icc CFLAGS ==

+

In general, icc supports many of the same CFLAGS gcc supports and is also pretty tolerant to gcc flags it cannot use. In most cases it will happily ignore the flag warning the user and moving on. For an exhaustive list and explanation of available compiler flags, consult the icc manpage or better yet by invoking the compiler with the help flag:

In general, icc supports many of the same CFLAGS gcc supports and is also pretty tolerant to gcc flags it cannot use. In most cases it will happily ignore the flag warning the user and moving on. For an exhaustive list and explanation of available compiler flags, consult the icc manpage or better yet by invoking the compiler with the help flag:

icc --help

icc --help

=== -xX ===

=== -xX ===

+

Use to generate specialized code to run exclusively on processors supporting it. If unsure which option to use, simply inspect the '''flags''' section of {{ic|/proc/cpuinfo}}. In the example below, '''SSE4.1''' would be the correct selection:

Use to generate specialized code to run exclusively on processors supporting it. If unsure which option to use, simply inspect the '''flags''' section of {{ic|/proc/cpuinfo}}. In the example below, '''SSE4.1''' would be the correct selection:

*1 - optimize for maximum speed, but disable some optimizations which increase code size for a small speed benefit

+

* 1 - optimize for maximum speed, but disable some optimizations which increase code size for a small speed benefit

−

*2 - optimize for maximum speed (DEFAULT)

+

* 2 - optimize for maximum speed (DEFAULT)

−

*3 - optimize for maximum speed and enable more aggressive optimizations that may not improve performance on some programs (recommended for math intensive looping programs)

+

* 3 - optimize for maximum speed and enable more aggressive optimizations that may not improve performance on some programs (recommended for math intensive looping programs)

+

+

=== -w ===

−

=== -w ===

Similar to the gcc:

Similar to the gcc:

−

*-w - disable all warnings (recommended for the package compilation)

+

* -w - disable all warnings (recommended for the package compilation)

−

*-Wbrief - print brief one-line diagnostics

+

* -Wbrief - print brief one-line diagnostics

−

*-Wall - enable all warnings

+

* -Wall - enable all warnings

−

*-Werror - force warnings to be reported as errors

+

* -Werror - force warnings to be reported as errors

== Software compiled with Intel C / C++ ==

== Software compiled with Intel C / C++ ==

−

In the following table we report a list of packages from the officials repository that we are tried to compile with the intel C/C++ compiler. The compilation should be done by using the PKGBUILD from ABS.

+

In the following table we report a list of packages from the officials repository that we have tried to compile with the intel C/C++ compiler. The compilation should be done by using the PKGBUILD from ABS.

Contents

Before you begin

Note: Packages that have been compiled by icc will depend on the associated libs contained in the intel-openmp package in order to run. Since intel-openmp depends on intel-compiler-base, users MUST have both packages installed at all times!

Setup and installation

intel-parallel-studio-xeAUR are available in the AUR. To build the package, one needs a license file which is free for personal and for non-commercial use. The requisite license file is emailed to users upon [registration] and should be copied into the $startdir prior to running makepkg. The current PKGBUILD assembles 7 or 8 packages:

Note: A minimal working environment requires the intel-compiler-base and intel-openmp packages; if you want also the fortran compiler you must install intel-fortran-compiler.

Using icc with makepkg

Note: Not every package will successfully compile with icc without heavy modifications to the underlying source.

There is currently no official guide to using icc with makepkg. This section is meant to capture various methods suggested by users. Please make a new sub-section with your suggested method titled as such.

Method 1 (12/08/2012)

Modify /etc/makepkg.conf inserting the following code under the existing line defining CXXFLAGS to enable makepkg to use icc. No special switches are needed when calling makepkg to build.

To toggle between the native gcc and icc, simple comment or uncomment the newly created _CC variable.

In some case the compilation method described above fails and the compilation will be performed with gcc, so you should test if yours application has been effectively compiled with icc.

To test if your package has been really compiled with icc:

Type the command ldd [your_app] | grep intel If the application is linked to a shared object located in the directory /opt/intel/lib/ it's mind that has been complied with icc.

Another method is to observe the build output and watch if it's using the icc or icpc command.

The last method is to watch if the warnings are in icc style or not.

icc CFLAGS

In general, icc supports many of the same CFLAGS gcc supports and is also pretty tolerant to gcc flags it cannot use. In most cases it will happily ignore the flag warning the user and moving on. For an exhaustive list and explanation of available compiler flags, consult the icc manpage or better yet by invoking the compiler with the help flag:

icc --help

-xX

Use to generate specialized code to run exclusively on processors supporting it. If unsure which option to use, simply inspect the flags section of /proc/cpuinfo. In the example below, SSE4.1 would be the correct selection:

Tip: Use the -xHost flag if unsure what your specific processor supports.

-Ox

Same behavior as gcc. x is one of the following options:

0 - disables optimizations

1 - optimize for maximum speed, but disable some optimizations which increase code size for a small speed benefit

2 - optimize for maximum speed (DEFAULT)

3 - optimize for maximum speed and enable more aggressive optimizations that may not improve performance on some programs (recommended for math intensive looping programs)

-w

Similar to the gcc:

-w - disable all warnings (recommended for the package compilation)

-Wbrief - print brief one-line diagnostics

-Wall - enable all warnings

-Werror - force warnings to be reported as errors

Software compiled with Intel C / C++

In the following table we report a list of packages from the officials repository that we have tried to compile with the intel C/C++ compiler. The compilation should be done by using the PKGBUILD from ABS.