can't start because libiomp5md.dll is missing from your computer

Hi all:

I met one problem when I use XE2015 with visual studio 2010 in windows 7, 64 bit.


The program can compiled successfully, but when I run it in CMD command window, I met the following error:


Can anyone tell me how to fix this? I am new to this, kindly let me know the detail procedure to solve this problem. Thanks in advance!

Introduction to OpenMP* on YouTube

Tim Mattson (Intel), has authored an extensive series of excellent videos as in introduction to OpenMP*. Not only does he walk through a series of programming exercises in C, he also starts with a background introduction on parallel programming.

Check out the series:

OpenMP* WORKSHARE 现在可与英特尔® Fortran 编译器 15.0 并行

英特尔® Fortran 编译器 15.0 现可为包含阵列分配的 OpenMP WORKSHARE 和 PARALLEL WORKSHARE 结构的指定实例生成多线程代码。  很显然,它们是使用 OpenMP SINGLE 结构进行部署,这表示仅可生成单线程代码。


OMP WORKSHARE 结构的数据块内的语句并非总是生成多线程代码。 一些语句进行并行化;另一些语句不进行并行化,而在 OMP SINGLE 结构内按顺序执行,以保持 WORKSHARE 的语义正确。




  • 开发人员
  • 教授
  • Apple OS X*
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • 服务器
  • Fortran
  • 高级
  • OpenMP*
  • 在Intel® MIC多核架构上使用OpenMP*库的编程及调优实践

        本文将主要介绍在Intel® MIC多核架构上运行及优化OpenMP*多线程程序的相关技术,且将围绕offload及native两种运行时执行环境展开详解。





  • C/C++
  • OpenMP*
  • Intel® Many Integrated Core Architecture
  • mfense question.

    Want to know in X64, does mfence  instruction flush the CPU cache globally, meaning :-

    If CPU0 does mfence, then does it invalidate its cacheline which contain the shared memory location, which is updated at CPU1. And it also results in CPU1 flush its cache containing that shared memory location ?

    In other words, if CPU0 does mfence, is it going to get the correct shared memory content which is updated at CPU1 ? Or CPU1 which has updated the shared memory, need to do mfence ? 

    Thanks a lot


    New code release

    We are excited to announce the next release of the Intel® OpenMP* Runtime Library at This release aligns with Intel® Parallel Studio XE 2015.



    New Features

    • Contribution from ScaleMP: stack padding.
    • Redesign of wait and release code; performance improvements.

    Bug Fixes

    订阅 OpenMP*