Intel Software Network articles Feed http://software.intel.com/en-us/articles/intel-parallel-composer-kb/type/technical-notes/ en-us Getting Started with Intel® Cilk™ Plus Array Notations Introduction

Array Notations is an Intel-specific language extension that is a part of Intel® CilkTM Plus feature supported by the Intel® C++ Compiler that provides ways to express data parallel operation on ordinary declared C/C++ arrays.  By using array notations, you can improve the performance of your application through Vectorization.  Vectorization is the key to improving your applications' performance through taking advantage of the processor's capability to operate on multiple array (or vector) elements at a time.  The Intel® Compilers provide unique capabilities to enable vectorization. The programmer may be able to help the compiler to vectorize more loops through a simple programming style and by the use of compiler features designed to assist vectorization.  This article discusses how to use the Array Notations feature from the Intel® CilkTM Plus, to help the compiler to vectorize C/C++ code and improve performance.

Click here to continue reading the article. ]]> http://software.intel.com/en-us/articles/getting-started-with-intel-cilk-plus-array-notations/ Sun, 25 Mar 2012 00:00:00 -0700 http://software.intel.com/en-us/articles/getting-started-with-intel-cilk-plus-array-notations/#comments http://software.intel.com/en-us/articles/getting-started-with-intel-cilk-plus-array-notations/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Getting Started with Intel® Cilk™ Plus SIMD Vectorization and Elemental Functions Introduction

SIMD Vectorization and Elemental Functions are a part of Intel® CilkTM Plus feature supported by the Intel® C++ Compiler that provide ways to vectorize loops and user defined functions.  Vectorization is the key to improving your applications' performance through taking advantage of the processor's Single Instruction Multiple Data (SIMD) capability to operate on multiple array (or vector) elements at a time.  The Intel® Compilers provide unique capabilities to enable vectorization. The programmer may be able to help the compiler to vectorize more loops through a simple programming style and by the use of compiler features designed to assist vectorization.  This article discusses how to use the vector elemental functions, and the SIMD directive (#pragma simd) from the Intel® CilkTM Plus, to help the compiler to vectorize C/C++ code and improve performance.

Click here to continue reading the article.

Additional information about what sort of loops may be vectorized using the SIMD pragma/directive is available here. ]]> http://software.intel.com/en-us/articles/getting-started-with-intel-cilk-plus-simd-vectorization-and-elemental-functions/ Tue, 20 Mar 2012 00:00:00 -0700 http://software.intel.com/en-us/articles/getting-started-with-intel-cilk-plus-simd-vectorization-and-elemental-functions/#comments http://software.intel.com/en-us/articles/getting-started-with-intel-cilk-plus-simd-vectorization-and-elemental-functions/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® MKL Data Fitting component: Overview Intel® MKL 10.3 update 8 introduces Data Fitting Component. Data Fitting functions in Intel® MKL provide spline-based interpolation capabilities that can be used for spline construction (Linear, Cubic Quadratic etc.), to approximate functions, function derivatives or integrals, and perform cell search operations.

Please find additional details in the overview training material: Intel MKL Data Fitting Library Overview.pdf


Note: 
1. Intel® MKL 10.3 update 8 supports 1-D data fitting components.
2. Data Fitting component of Intel® MKL 10.3 update 8 does not support PGI* Fortran Compiler.


]]> http://software.intel.com/en-us/articles/mkl-data-fitting-component-overview/ Sun, 04 Dec 2011 10:30:00 -0800 http://software.intel.com/en-us/articles/mkl-data-fitting-component-overview/#comments http://software.intel.com/en-us/articles/mkl-data-fitting-component-overview/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel® Math Kernel Library (Intel® MKL) : What's deprecated? Please see below for details on the deprecated functionalities in Intel® Math Kernel Library (Intel® MKL).

Forthcoming Intel® MKL 11.0 (Expected date of release: Autumn 2012)

•  Intel® MKL 11.0 will have backward incompatibility with Intel® MKL 10.2 update 3

•  Open MP static library on Microsoft* Windows

•  GMP* Arithmetic functions

•  Intel® MKL Reference Manual will be removed from product package

•  Intel® Pentium® III Processors will no longer be supported

•  Red Hat* EL4 and PGI* Fortran 10.x support will be dropped

•  PGI* Fortran 77 support will be removed

 

Please send us your comments at Intel® Premier Support or the Intel® MKL user forum.

 

 

 

 

]]> http://software.intel.com/en-us/articles/intel-mkl-whats-deprecated/ Thu, 01 Dec 2011 00:00:00 -0800 http://software.intel.com/en-us/articles/intel-mkl-whats-deprecated/#comments http://software.intel.com/en-us/articles/intel-mkl-whats-deprecated/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Cluster Toolkit for Linux* Knowledge Base Intel® Cluster Toolkit for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Parallel Composer Knowledge Base Different behavior of Intel C Compiler on Linux/Windows 
int main() {

  int i;
  i = 1;
  printf("Here we go\n");
  int j;
  j = i;

}


>icl -c t.c
Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 12.1.0.233 Build 20110811
Copyright (C) 1985-2011 Intel Corporation.  All rights reserved.

t.c
t.c(6): error: declaration may not appear after executable statement in block
    int j;
    ^

compilation aborted for t.c (code 2)

To be able to declare variables after executable statements rather than having to declare all of them up front you will need to compile per C99 specification using the compiler option /Qstd=c99 as shown below:

>icl -c t.c -Qstd=c99
Intel(R) C++ Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 12.1.0.233 Build 20110811
Copyright (C) 1985-2011 Intel Corporation.  All rights reserved.

t.c
>

 

]]> http://software.intel.com/en-us/articles/different-behavior-of-intel-c-compiler-on-linuxwindows/ Wed, 07 Sep 2011 00:00:00 -0700 http://software.intel.com/en-us/articles/different-behavior-of-intel-c-compiler-on-linuxwindows/#comments http://software.intel.com/en-us/articles/different-behavior-of-intel-c-compiler-on-linuxwindows/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base No "Intel(R) C++ Project" entry in VS2008 IDE
There is no "Intel(R) C++ Project" entry in the VS2008 IDE.  The way it works is that the user creates a Microsoft* C++ project (e.g. Win32 Console Application, Win32 project, etc.), and then uses the Intel Compiler integration plug-in in Visual Studio to build that project with the Intel C++ compiler.  Here's how it works:

1. Create a C++ project using Visual Studio or load an existing VC++ project

2. Right click the Solution name in Visual Studio Solution Explorer, or right click on single project or a select number of projects in the solution (e.g. CTRL-Click projects of interest and then right click)

3. Click "Intel C++ Composer XE 2011" and then click  "Use Intel(R) C++"

After the above step if you do a "Build" or "Rebuild" the selected projects will be built using the Intel C++ Compiler.


]]> http://software.intel.com/en-us/articles/no-intelr-c-project-entry-in-vs2008-ide/ Wed, 07 Sep 2011 00:00:00 -0700 http://software.intel.com/en-us/articles/no-intelr-c-project-entry-in-vs2008-ide/#comments http://software.intel.com/en-us/articles/no-intelr-c-project-entry-in-vs2008-ide/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Parallel Studio 2011 SP1 Release Notes This page provides the current Installation Guide and Release Notes for the Intel® Parallel Studio 2011 SP1 product. All files are in PDF format - Adobe Reader* (or compatible) required.

To get product updates, log in to the Intel® Software Development Products Registration Center

For questions or technical support, visit Intel® Software Developer Support

Version 2011 SP1 Initial release, September 6, 2011: release_notes_studio.pdf

]]> http://software.intel.com/en-us/articles/intel-parallel-studio-2011-sp1-release-notes/ Wed, 31 Aug 2011 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-parallel-studio-2011-sp1-release-notes/#comments http://software.intel.com/en-us/articles/intel-parallel-studio-2011-sp1-release-notes/ Intel® Parallel Amplifier Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Parallel Inspector Knowledge Base Intel® Parallel Advisor Knowledge Base Which Intel® Math Kernel Library (Intel® MKL) libraries are "Redistributables"?
1. Copy Intel MKL dlls (for Widnows*) from directory redist\(ia32\intel64)  to your destination application folder. For Linux and Mac OS* shared objects, .so files are located in redist\(ia32/intel64) directory.

2. Create your own dll for your redistributions by using Intel MKL customdll linkage.

3. Use Intel MKL static libraries from \lib directory.

If you are using Intel MKL stand-alone product:

Check the redist.txt file located in <Intel MKL install directory> \Documentation\en_US\mkl for more details


If you are using Intel MKL from previous Intel® Compiler Professional Edition version:

Check the redist.txt file located in Intel MKL directory <Intel MKL install directory> \Documentation\en_US\mkl for more details.



]]> http://software.intel.com/en-us/articles/which-mkl-libraries-are-redistributables/ Wed, 25 May 2011 08:30:00 -0700 http://software.intel.com/en-us/articles/which-mkl-libraries-are-redistributables/#comments http://software.intel.com/en-us/articles/which-mkl-libraries-are-redistributables/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Math Kernel Library Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Intel® Parallel Building Blocks: Quickly Write Parallel Tasks Using Intel® Cilk™ Plus Keywords and Reducers Technical Presentation Questions and Answers
Technical Presentation Recording


Presentation Slides


Information on upcoming presentations


Q: What is different of reducer behavior of reducer = reducer + ... and reducer += ...

A: There is no difference.


Q: How do we catch exceptions raised from spawned functions?

A: If an exception is thrown by both branches of a spawn (i.e., from the spawned function and from the continuation after the spawn), then the exception that is caught is the one that would have occurred first in the serialization of the program. The other exception is discarded. Refer to the compiler User’s Guide for the details on exception handling with Cilk Plus codes.


Q: What is the significance of hyper threading on thread count?

A: It’s documented that the default number of Cilk Plus workers is tied to physical core count, but we have seen reports that the default is instead using the number including virtual hyper-threading cores as well. We are investigating.


Q: General question regarding PBB: which is appropriate for "large data" heavy-compute jobs?

A: Intel® Array Building Blocks should be the first solution you look at. Cilk Plus array notations and elemental functions may also be interesting.


Q: Does Inspector XE support Intel® Cilk™ Plus?

A: Yes, with some significant limitations. See http://software.intel.com/en-us/articles/support-for-intel-cilk-plus-in-intel-parallel-inspector-2011/.


Q: In the parts assembly example, the code modification was to a section of the code outside the cilk_for. Why is that? Is that part of the code getting parallelized also?

A: You’ll notice that the body of the cilk_for was a recursive call to the walk() function. So even though the code in question was outside the cilk_for, it was inside walk() and therefore could be called in parallel. The reducer construct is unique among parallel reduction constructs in that it is not directly tied to the for loop being parallelized.

]]> http://software.intel.com/en-us/articles/quickly-write-parallel-tasks-using-intel-cilk-plus-keywords-and-reducers-technical-presentation-questions-and-answers/ Thu, 20 Jan 2011 00:00:00 -0800 http://software.intel.com/en-us/articles/quickly-write-parallel-tasks-using-intel-cilk-plus-keywords-and-reducers-technical-presentation-questions-and-answers/#comments http://software.intel.com/en-us/articles/quickly-write-parallel-tasks-using-intel-cilk-plus-keywords-and-reducers-technical-presentation-questions-and-answers/ Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base How to prevent source code full path location information from being visible in an executable
Problem : When using the -openmp  or -parallel compiler options under linux* or Mac OS* X, or the /Qopenmp or /Qparallel options under Windows, the resulting executable files contain the full pathnames to the source files for each source file containing an OpenMP or Parallel region.   This was done to allow Intel profiling and correctness checking tools to be able to find and display source information in the analysis tools.


Environment : Windows*, Linux*, Mac OS* X, all compilers since 9.1 versions

Root Cause :
The Intel compilers by default included source file full path information so that Intel analysis tools could find source files during analysis for correctness or performance.

Resolution :
With the release of Intel Composer XE ( aka version 12.0 ) an option was included to allow removing this source path information from the executable header information:

Linux and Mac OS X:   -no-parallel-source-info  compiler option should be used
Windows:     /Qparallel-source-info-   compiler option should be used

These options are only available in the 12.0 aka Composer XE compiler products.  If you are using an older version, please upgrade to 12.0.

]]> http://software.intel.com/en-us/articles/how-to-prevent-source-code-full-path-location-information-from-being-visible-in-an-executable/ Thu, 16 Dec 2010 20:00:00 -0800 http://software.intel.com/en-us/articles/how-to-prevent-source-code-full-path-location-information-from-being-visible-in-an-executable/#comments http://software.intel.com/en-us/articles/how-to-prevent-source-code-full-path-location-information-from-being-visible-in-an-executable/ Intel® Parallel Composer Intel® Cluster Toolkit Compiler Intel® Compilers Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Cluster Toolkit for Linux* Knowledge Base Intel® Cluster Toolkit for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Parallel Composer Knowledge Base