Intel® C++ Compiler

parallel studio 2015 unable to compile C++11 code

I am trying to compile a c++ code which uses C++-11 features. The code can be build with gcc-4.8.3 using the following command

g++ -std=c++11 main.cpp sequitur/*.cpp

However, I am not able to compile it on Parallel Studio XE 2015. Although Visual studio 2013 doesn't fully implement C++-11 features, the ICL reports some error in the visual studio header files. I know that visual studio is unable to build that. I have installed parallel XE 2015 to use ICL features.

 

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

Hi,

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

template
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?

Thanks,
Simon

Beginner choice

I'm learning WinAPI and like to play around with C++ for it.
Does the compiler really matters to this kind of task?
What Intel's compiler can do beyond MS C++? What is it for, exactly?
I also want to do some OpenGL programming? Does it help on it?
 

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.

Switching back to vc++: Cannot get rid of /fast option

I've been experimenting with the Intel compiler for the past few weeks, and decided to go back to the VC++ compiler.  I right clicked on the solution and selected "use vc++" compiler.  Tried to build, and got a bunch of warnings about "ignoring unknown option /fast".  I uninstalled the Intel compiler, completely blew away the development directly, got latest from source control, and the warnings are still there.  I searched all of the files in the dev directory (including property sheets and project settings) for the /dev flag.  Nothing. 

订阅 Intel® C++ Compiler