Intel® C++ Compiler

Webinar on 9/27/2017 9am PST on Better Threaded Performance and Scalability with Intel Vtune Amplifer + OpenMP*

Webinar Topic: Better Threaded Performance and Scalability with Intel Vtune Amplifer + OpenMP*

Date: Wednesday, September 27, 2017 9 AM PDT

Abstract: Modern generation of Intel(R) Processors come with multiple processing cores and each core offering SIMD registers. This makes it all the more important for Application Developers to be aware of how to utilize all the processing cores efficiently. This webinar will walk step by step on the following concepts using a simple Edge Detection application:

Intel® C++ Compiler 18.0 has been released as part of Intel Parallel Studio XE 2018

Intel® Parallel Studio XE 2018, including Intel® C++ Compiler 18.0, is now available from the Intel Registration Center. Release notes can be found

Some of the new supported features are below:

Оптимизировали, оптимизировали, да не выоптимизировали!

Оптимизация? Конечно, каждый сталкивался с данной задачей при разработке своих, сколь-нибудь значительных, требующих определённых вычислений, приложений. При этом способов оптимизировать код существует огромное множество, и, как следствие, различных путей сделать это в автоматическом режиме с помощью опций компилятора. Вот здесь и возникает проблема – как выбрать то, что нужно нам и не запутаться?

Vectorization with OpenMPv4 and performance portability across compilers



I am developping some vectorized code with OpenMP v4 and I am really happy with the performance I get with Intel compilers. Unfortunately, both gcc 7.2.0 and clang 5.0.0 make a mess of those (#pragma omp simd) and give very bad performance. This make the use of OpenMP v4 non portable across compilers in terms of performance. This makes writing software for AVX, AVX2 and AVX512 quite difficult as intrinsics seems to be the only solution if you want to get good performance across compilers.

Disable remarks/warnings/messages temporarily

Hi, I'm new to the Intel compiler having previously used Visual Studio C++ compiler. With VS we would use a #pragma to disable various warnings just before including third party headers but then re-enable them after inclusion (there's no way we can fix those warnings and we don't want our output flooded with things we can't change as it makes it harder to see things we are doing wrong ourselves).

Assertion failure at kmp_runtime.cpp(6480)

The following error is being reported on OSX




OMP: Error #13: Assertion failure at kmp_runtime.cpp(6480)
OMP: Hint: Please submit a bug report with this message, compile and run commands used, and machine configuration info including native compiler and operating system versions. Faster response will be obtained by including all program sources. For information on submitting this issue, please see

Subscribe to Intel® C++ Compiler