Intel® C++ Compiler

Conditional compilation bug or feature ?


I have a software that has 2 versions of an implemented algorithm, so it used different versions of the same class (in my case its SSE vs AVX, but really, it's not relevant) in 2 different compiler units, and suprisingly the linker take the initiative of taking an arbitrary one.

Is it a bug (that I reproduced as well in Microsoft and GCC compiler) or a feature (if that so can someone help me finding where this behavior is specified) ?

Here is how to reproduce the problem:


Optimization features.


I'd like to talk about two weird things in the optimization process of the compiler.

#1 : sqrtsd seems preferred over sqrtpd... (just did a 30% performance boost by forcing the use of 2 sqrtpd instead of the 4 sqrtsd previously generated in my code). I know it's not often that sqrt is used sequentially so I won't mind if that feature doesn't appear. However here comes #2.

questions about intel C++ studio XE 2013

Q:intel C++ studio XE 2013 when does next version come out?
Q:intel C++ studio XE 2013 does this c++ compiler come with any build tools?
Q:intel C++ studio XE 2013 what can I do if I find a compiler bug? do compiler fixes come with the price?
Q:intel C++ studio XE 2013 what type of license is this? am hoping for single-user at least.


The Chronicles of Phi - part 4 - Hyper-Thread Phalanx – tiled_HT2

The prior part (3) of this blog showed the effects of the first-level implementation of the Hyper-Thread Phalanx. The change in programming yielded 9.7% improvement in performance for the small model, and little to no improvement in the large model. This left part 3 of this blog with the questions:

What is non-optimal about this strategy?
And: What can be improved?

There are two things, one is obvious, and the other is not so obvious.

Data alignment

Intel(R) C++ Compiler and Intel(R) Fortran Compiler Do not Work with XCode 5.1*

Reference Number : DPD200254375

  • Intel(R) C++ Composer XE 2013 for OS X* (including update 2)
  • Intel(R) Fortran Composer XE 2013 for OS X* (including update 2)

Problem Description:

If you have recently upgraded to the latest XCode 5.1*, the Intel C++ compiler or the Intel Fortran compiler is not integrated into XCode any more. So the existing projects that are built with Intel C++ compiler or Intel Fortran compiler will fail when building.

Solution Status:

  • Developers
  • Apple OS X*
  • C/C++
  • Fortran
  • Intel® C++ Compiler
  • Intel® Fortran Compiler
  • XCode
  • icc crash


    I get a crash when trying to compile a C/C++ program with icc

    icc -O3
    ": internal error: ** segmentation violation signal raised **
    Access violation or stack overflow. Please contact Support.

    compilation aborted for (code 4)


    icc (ICC) 14.0.2 20140120
    Copyright (C) 1985-2014 Intel Corporation.  All rights reserved.

    System: CentOS 6.5 Linux, 64 bit (kernel version: 2.6.32-431.5.1.el6.x86_64)

    Subscribe to Intel® C++ Compiler