Compilatore C++ Intel®

x64 Merge Module


We have recently switched to the Intel compiler (Composer XE 2015) and we are trying to use WIX to create an installer for our product. We are currently having an issue with the x64 merge module (w_ccompxe_redist_intel64_2015.3.208.msm), WIX throws the following error:

light.exe(0,0): error LGHT0204: ICE80: This 32BitComponent Comp_cilkrts20.dll.D9F09DDD_F3FE_427A_A63E_83D87E7D99CC uses 64BitDirectory compiler.D9F09DDD_F3FE_427A_A63E_83D87E7D99CC

We have been using the Microsoft merge modules for several years and had no issues.

游戏公司借助英特尔® Sample Code 加速发展

Whether you are an indie game developer or a seasoned professional, you are likely to find an interesting code sample on Intel Developer Zone's game dev section. Read here to learn how Intel engineers worked with Blizzard and Codemasters to optimze our Adaptive Volumetric Shadow Maps (AVSM), Conservative Morphological Anti-Aliasing (CMAA), and Software Occlusion Culling code samples.
  • Sviluppatori
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 10
  • Microsoft Windows* 8.x
  • Sviluppo di videogame
  • Windows*
  • C/C++
  • Compilatore C++ Intel®
  • Microsoft DirectX*
  • samples we’ve created have been adapted for use in games published by Blizzard and Codemasters – specifically Adaptive Volumetric Shadow Maps (AVSM)
  • Conservative Morphological Anti-Aliasing (CMAA)
  • and Software Occlusion Culling.
  • Sviluppo di videogame
  • Grafica
  • Processori Intel® Core™
  • Desktop Microsoft Windows* 8
  • Ottimizzazione
  • 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!

    Iscriversi a Compilatore C++ Intel®