Intel® C++ Compiler

Webinar on Accelerate Application Performance with OpenMP* and SIMD Parallelism

We welcome you all for the webinar tomorrow morning at 9am PST where Martyn Corden is going to show you how to tune a SAD kernel using Intel Software Tools. He will walk thru the steps on how to look for tuning opportunities and optimize the kernel step by step incrementally (also show performance improvement after each step). Please register at to attend this webinar.

Thanks and Regards

Join the Intel® Parallel Studio XE 2018 Beta program

We would like to invite you to participate in the Intel® Parallel Studio XE 2018 Beta program. In this beta test, you will gain early access to new features and analysis techniques. Try them out, tell us what you love and what to improve, so we can make our products better for you. 

Registration is easy. Complete the pre-beta survey, register, and download the beta software:
           Intel® Parallel Studio XE 2018 Pre-Beta survey

Intel C++ Compiler 16.0 is now available in Intel Parallel Studio XE 2016

The new version Intel C++ Compiler 16.0 is now available in Intel Parallel Studio XE 2016 that has launched early this week. If your support license is current you can download and install this at no additional charge from the Intel Registration Center

You will find some blog postings about some new features and new free tools.

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

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

Strange segmentation faults of 3 SPEC_CPU_2017 fprate benchmarks

Hi guys,

I compiled and statically linked binaries from the SPEC CPU 2017 benchmark suite. But there are three fprate benchmarks always giving strange segmentation faults. They are '503.bwaves_r', '521.wrf_r' and '527.cam4_r', and the following is the 503.bwaves_r error message. Could anyone shed light on the root cause of the issue and how it can be resolved?

The ICC version is 17.0.4. The flags that I used for compilation and linking are as follows: 

Visual Studio Help in Chrome


The Intel manuals in Visual Studio open in the default browser, which for me is Google Chrome.

Since the latest release, these now show blank pages.

I am guessing that they set 3rd party cookies, which are blocked in my browser settings.

How can I whitelist the Intel manuals without allowing 3rd party cookies from all sites?


I am using Intel Compiler 17.0 in VS 2017 Community in Windows 10.

libmmd.lib and other static libs usage for projects built using MSVC

Hi All,

We are using MS Visual Studio 2015 and Intel C++ Compiler 2017. All of our code is built using Intel compiler. We provide this code to others in form of dll files and associated lib that are  expected to be dynamically linked in their application. These applications are not built using Intel Compiler. When dynamically linking the application, we get an error that libmmd.lib is required. The application of course does not explicitly linked with libmmd.lib nor is it built using Intel compiler. 

Suscribirse a Intel® C++ Compiler