Restrictions When Programming on Windows* for Intel® MIC Architecture

This topic only applies when targeting Intel® Many Integrated Core Architecture (Intel® MIC Architecture).

Several programming features that are specific to Windows* might result in errors when you use them in an offload compilation for Intel® MIC Architecture, even if you do not use these features in the code or data that is actually offloaded. When you use code with these features in your application, you must correctly structure the code so that it is not visible in a target compilation.

These features include, but are not limited to:

• Windows calling conventions. For example:

  !DIR$ ATTRIBUTES STDCALL :: PROCX

• Theattributes DLLEXPORT and DLLIMPORT. For example:

  !DIR$ ATTRIBUTES DLLIMPORT :: VARX

• Module files or libraries that are specific to Windows, such as IFNLS or IFQWIN.

In addition, you must take care to ensure that code does not depend on specific data size or order of allocation of data, as these can vary between the host and the target.