Known Issues

Compilation error with #import "XXX.dll" when building the x64 configuration inside Visual Studio 2010* and Visual Studio 2012*

Reference Number: DPD200242942

Product Version: Intel C++ Composer XE 2013 for Windows update 3 only

Operating System: Windows

Problem Description:

When building your program for "x64" configuration inside Visual Studio 2010* or Visual Studio 2012 with the Intel C++ Compiler 2013 update3, you will get a compilation error if your code contains "#import <xxx.dll>" like:

  • C/C++
  • Avoiding Potential Problems - the __MIC__ macro and offload code blocks

    The __MIC__ macro is used to protect source code which is intended to run only on the coprocessor. For example:

    __declspec( target (mic))

    void is_it_on_coprocessor()

    {

      #ifdef __MIC__

        printf("yes, it is\n");

      #else

        printf("no, it is not\n");

      #endif

    }

    Using -par-affinity results in linker error undefined reference to `__kmpc_set_defaults'

    Reference Number: DPD200240320

    Version: Intel® C++ and Fortran Composer XE 2013, compilers 13.0 and 13.1

    Product: Intel® C++ and Fortran Composer XE

    Operating System: Windows*, Linux*, OS X*

    Problem Description: In the Intel® Composer XE 2011 C++ and Fortran compilers (versions 12.0 and 12.1), the compiler silently ignored the /Qpar-affinity and -par-affinity compiler options. This was fixed in Intel Composer XE 2013, but this exposed another issue with the option's implementation that now causes a linker error.

  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • Apple macOS*
  • C/C++
  • Fortran
  • Intel® C++ Compiler
  • Intel® Fortran Compiler
  • Development Tools
  • BIOS preventing access to QPI performance counters

    Are you experiencing issues with accessing the performance counters to measure QPI traffic on Intel Xeon processors E5 family? For examples, you might run into the following error message when you try to execute Intel Performance Counter Monitor (Intel PCM) on such a system:

  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Server
  • Advanced
  • PMU Performance Monitoring PerfMon
  • Bug report IVF Composer XE 2013 Update 2 VS2008 error #10037: could not find 'link'

    Bug Report  March 2013

    Affected version:  Intel(R) Visual Fortran Composer XE 2013 Update 2 ( version 13.1.0.149 / build 20130118 ) when used in conjunction with Visual Studio 2008

    Symptoms/behavior: after upgrading to IVF Composer XE 2013 Update 2 builds fail with "error #10037: could not find 'link'".  Root cause is a bug in the Intel Integrations into Visual Studio.  The integration into Visual Studio 2008 introduced a faulty path.  This will be fixed in an upcoming Update release.  There is a work around:

  • Microsoft Windows* (XP, Vista, 7)
  • Fortran
  • Intel® Parallel Studio XE Composer Edition
  • Bug report IVF Composer XE 2013 Update 2 Visual Studio crashes opening Fortran source file

    Affected Version:  Intel(R) Visual Fortran Composer XE 2013 Update 2 ( version 13.1.0.149 / build 20130118 )

    Symptom:  Visual Studio 2010 environment will crash when opening a Fortran Source file

    Root cause:  the Visual Fortran Integrations into Microsoft Visual Studio introduced a bug in the Update 2 compiler.  Fortran source files containing:

    interface assignment(=)

  • Microsoft Windows* (XP, Vista, 7)
  • Fortran
  • Advanced
  • Beginner
  • Intermediate
  • Intel® Parallel Studio XE Composer Edition
  • Link error with icpc when using Boost* 1.51+ MPL library and g++*

    Problem

    Link error with icpc: when linking object files compiled with icpc & g++* along with Boost* MPL library 1.51 or above, as shown in the sample test case below:

    %cat t.h
    #include <boost/mpl/vector.hpp>
    template<typename T> struct my;
    void foo(my<boost::mpl::vector<> >* = 0);

    %cat u.cpp
    #include "t.h"
    int main() { foo();}

  • Linux*
  • Microsoft Windows* 8.x
  • C/C++
  • Intermediate
  • Intel® Parallel Studio XE
  • Intel® Parallel Studio XE Composer Edition
  • Intel® Parallel Studio XE Professional Edition
  • Development Tools
  • Inspector XE 2013 changed the usage of appdebug option

    We know that Inspector XE has realized the connection to GDB seamlessly when Inspector detects an error, I described the usage in this article for Inspector XE 2011. However if you try this function on Inspector XE 2013 according to my blog, will meet below error:

    # inspxe-cl -collect mi3 -knob appdebug=on-error -- ./test_memory.gcc
    Error: Cannot find knob appdebug. Use -knob-list to see available knobs.

    Subscribe to Known Issues