Compilateur Intel® C++

Option to suppress xilink output messages?

I'm using SCons to build a project with ICC on Windows, and I get a lot of xilink messages in the console that look like this:

xilink: executing 'link'
   Creating library path\to\file\file.lib and object path\to\file\file.exp

I believe these messages are output to stderr and are really polluting my console. I found no ICC option to suppress them. What's the proper way to do this, apart from the brute-force and sub-optimal forwarding of stderr output to NUL?


What other arguments does -qopenmp enable?

We have added "-qopenmp" to the compilation and linking commands for a serial code, and numerical results changed slightly. That is, there are no OpenMP pragmas in the code, no OpenMP support functions, and omp.h is not included, but the results are slightly different. I need to track down the cause of the changes.

Can anybody please advise what other compiler arguments -qopenmp sets? I want to experiment with enabling/disabling some of these arguments to find the cause of the difference.

OS X* 10.11 Support in Intel® Parallel Studio XE 2016

OS X 10.11 (El Capitan) introduces a new security policy called System Integrity Protection. In 10.11, the following directories can only be written to by the system (System-Only Locations): /bin, /sbin, /usr, /System, /Applications/Utilities. In contrast, the following directories are available to any process (Locations Available to Developers): /usr/local, /Applications, [~]/Library. This security policy affects Intel® Parallel Studio XE 2016 (IPS XE), because IPS XE creates symbolic links in /usr/bin for compilers to be properly recognized by Xcode IDE. IPS XE 2016 Update 1 officially supports OS X 10.11, and it creates symbolic links in /usr/local/bin.
  • Développeurs
  • Apple OS X*
  • Intel® Parallel Studio XE
  • Intel® Parallel Studio XE Composer Edition
  • Intel® Parallel Studio XE Professional Edition
  • Compilateur Intel® C++
  • Compilateur Intel® Fortran
  • Outils de développement
  • Vectorization with SIMD-enabled functions works from functions, not from main()


    I have run into a situation that I cannot explain. I have a loop with a SIMD-enabled function and I use #pragma simd before it. This loop vectorizes if it is placed in a separate function, but does not vectorize if it is inside main(). I am using Intel C++ compiler Please see code and vectorization reports below. Can anyone explain what is happening and if there is a way to work around this?

    This is

    Visual Studio 2015 integration


    I had Visual Studio 2012 on Windows 2012 server installed with Intel C/C++ composer 2013 edition - all working fine for years.

    I then recently purchased an upgrade to Intel PS XE 2016 Cluster edition, installed it with VS2012 addon option - all working fine. I can now compile my VS2012 projects using Intel C/C++ 2016. 

    I then installed Visual Studio 2015 Community. The installation succeeded (and I remembered to include Visual C++ tools). The problem is now:

    Schedule for C++14 support

    Hi folks,

    From I know that at least some C++14 features are supported by the 16.0 version of the C++ compiler. I was wondering if there is a (tentative) schedule available that shows when the remaining C++14 features will be implemented?



    S’abonner à Compilateur Intel® C++