Compilateur Intel® C++

Free webinar April 7 2015 9am PST "Further Vectorization Features of the Intel Compiler"

There is a free webinar “Further Vectorization Features of the Intel Compiler” coming next Tuesday talking specifically about getting more vectorizations from Intel Compilers. But you would benefit it more if you've watched/listened to the previous webinar Performance essentials using OpenMP* 4.0 vectorization with C/C++.

Intel® Xeon Phi™ Coprocessor code named “Knights Landing” - Application Readiness

As part of the application readiness efforts for future Intel® Xeon® processors and Intel® Xeon Phi™ coprocessors (code named Knights Landing), developers are interested in improving two key aspects of their workloads:

  1. Vectorization/code generation
  2. Thread parallelism

This article mainly talks about vectorization/code generation and lists some helpful tools and resources for thread parallelism.

  • Développeurs
  • Serveur
  • Intermédiaire
  • Compilateur Intel® C++
  • Intel® AVX-512
  • Knights Landing
  • Intel SDE
  • Intel® IMCI
  • Intel® Many Integrated Core Architecture
  • Informatique parallèle
  • Vectorisation
  • Оптимизировали, оптимизировали, да не выоптимизировали!

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

    compiler option O0 and O2 generate different results

    Hi all,

    I am optimizing my code. When I use O2 compiler option, the code runs repeatedly two times, the results are different in each repeat. But when I change to O0 compiler option, the results are the same. What might be the reason?

    BTW, I am using CentOS 6.5 and the command line is as follows:

    icpc -O2 -DALIGN_OPT=16 -DSSE -ipo main_turbo_decoding_cfunc.cpp turbo_decoding_cfunc.cpp -o turbo_decoding -lrt

    Thank you!

    Incomplete C++11 "alignas" implementation


    icc 15.0 gives me a warning when compiling the following code:

    using type alignas(64) = T;

    warning #3463: alignas does not apply here
    using type alignas(64) = T;

    If I understand correctly my code is correct, and indeed GCC and Clang compile it properly without warnings. Is this a known issue with icc? Can I expect a fix in future versions?


    FATAL ERROR - ICC generates dysfunctional code on OSX 32-bit (plus ICC crashes when compiling debug version)

    I use ICC on Windows and OSX. On Windows everything is fine. On OSX my project (release version) compiles just fine on 64-bit architecture. But on 32-bit it creates a malfunctioning code that crashes with a call stack containing a single line, saying that it crashed in operator delete(void*, void*). Note, it's the same code (except system services of course) on Windows 32 & 64 and Mac 32 & 64 and ONLY Mac 32 doesn't work. I'm having everything up to date (XCode, OSX, ICC), ICC is called from commandline.

    S’abonner à Compilateur Intel® C++