Development Tools

16.0.1 ICE with -standard-semantics -QxAVX -Qopt-report

Correction to my previous comment on this subject.  I had been using a hidden setting of -standard-semantics for recent versions of ifort.  Now with 16.0.1 the combination of options  -standard-semantics -Qxhost -Qopt-report produces internal compiler error while processing maxloc.  If I remove opt-report it runs, but optimization of maxloc is disabled.   Setting -assume:old_maxminloc fixes the ICE and restores optimization.  I assume this makes the 0-length operand case non-conformant with f2003 but didn't test that.  Setting -arch:SSE4.1 also avoids the ICE.

Memory leak?

With this piece of test code memory seems to leak. Am I doing something wrong?

    mfxVersion min_version;

    min_version.Major = 1;
    min_version.Minor = 0;

    m_mfxSession.Init(MFX_IMPL_HARDWARE_ANY, &min_version);

I'm using the video driver dated 5/25/2015, version

Nov. 18-19 IoT Commercial Developer Kit Workshop Materials

On November 18-19 Intel held a workshop titled the Intel IoT Commercial Developer Kit Workshop.  Materials used in support of this event included:

Presentations (see .zip at the bottom of the page)

Labs - do the following steps

1. Go to and click Download ZIP

  • Professional
  • Internet of Things
  • Development Tools
  • Intel® IoT Gateway
  • Internet of Things
  • MFX/MSDK and OpenCL interop on Linux ?

    Hi, I am planning to optimize one of my modules with OpenCL.

    I am using CentOS 7.1 and MSDK 2015R6. I looked up the example/sample codes provided by Intel. Two examples that deal with MSDK and OpenCL interop are all for Windows, as they both depend on the function clEnqueueAcquireDX9MediaSurfacesKHR() to use media surfaces as OpenCL memory objects, and that function only works with the DX9 adapter API.

    Two other examples (motion estimation) that do work on Linux appear to be just OpenCL. I don't see MSDK and OpenCL interop in them.

    rc.exe not found

    When I am trying to compile Fortran using the visual studio and Intel Fortran, I receive this error message "This project is out of date / Debug Win32" in a dialogue/ Would you like to build it?. When I click yes, there are always two error messages:

    Error (1): rc.exe not found.

    Error (2): error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb

    Explanation of how node-locked licenses works with new licensing?


    I am looking for an explanation of how Parallel Studio XE 2016 compiler licensing now works for renewals of 'existing' node-locked licenses.

    For example, I just installed XE 2016 on a windows machine with 3 ethernet adapters.

    In the license management for my serial #, it shows 3 adapters host IDs ( of my 3 adapters). And no way to manage them?

    Frankly, the new licensing is a real PITA. This is a big backward step.








    How to Change the Target type drop-down to Correctness Analysis


    This is my first post to the forum.
    I am testing advisor_xe_2016.1.0.423501 on a E5-2690 v3 cpu using the nqueens tutorial.
    According to the html doc "Predict Parallel Data Sharing Problems", i should be able to:

    Change Intel Advisor Project Properties:
    In the Intel Advisor GUI, choose File > Project Properties....
    In the Analysis Target tab:
    Change the Target type drop-down to Correctness Analysis.

    Catastrophic error with v16.0/1 but not with v15.x


    The update 1 and initial release of ifort v16 are leading to a catastrophic error during the compilation of a large fortran code (>100kLOC) while everthing is ok with v15.x.

    For the same code, v15 takes about 5min to compiler the entire code and v16 try to compile during several hours, and then crashes (the same compilation option being used).

    So there is definitely something going wrong with v16.

    The problem is, I have no way to make a short reproducible example.

    Moreover, I do not have an intel premium account.

    Subscribe to Development Tools