<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic As the preceding reply in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747263#M2503</link>
    <description>&lt;P&gt;As the preceding reply indicated, OpenMP 3.1 bits were still being introduced in the later 13.1 compiler updates (XE2013) so it would not be surprising that you must use the Intel proprietary equivalents KMP_AFFINITY to work with 11.1 compiler, if you didn't use the newer open sourced version of Intel OpenMP library.&lt;/P&gt;</description>
    <pubDate>Fri, 22 Nov 2013 17:52:56 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2013-11-22T17:52:56Z</dc:date>
    <item>
      <title>Intel OMP_PROC_BIND implementation</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747257#M2497</link>
      <description>Hello everybody,&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;I am doing an OpenMP implementation in Intel Fortran. I was really happy to see OpenMP 3.1 implemented because it would mean a nice cross-platform way of forbiding unwanted thread migration usingOMP_PROC_BIND. I set to true and it works fine on Intel architectures, but as soon as I tried it on an AMD Opteron I get this message:&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Warning #72: KMP_AFFINITY: affinity only supported for Intel processors.&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;OMP: Warning #71: KMP_AFFINITY: affinity not supported, using "disabled".&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;So, I guess the openmp library is implemented using kmp_affinity which by itself is supported only on Genuine Intel processors? What are my choices? Should I try linking with the OS (gnu) openmp library when and if they implement this feature? Should I give up of the possibility having a cross platform and cross-system way of thread binding?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks a lot,&lt;/DIV&gt;&lt;DIV&gt;Petros&lt;/DIV&gt;</description>
      <pubDate>Fri, 20 Apr 2012 07:38:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747257#M2497</guid>
      <dc:creator>Petros</dc:creator>
      <dc:date>2012-04-20T07:38:19Z</dc:date>
    </item>
    <item>
      <title>Intel OMP_PROC_BIND implementation</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747258#M2498</link>
      <description>&lt;P&gt;Thanks for pointing out this problem. Wewill address this issue in an upcoming compiler release.&lt;BR /&gt;Regards,&lt;BR /&gt;Jay&lt;/P&gt;</description>
      <pubDate>Mon, 30 Apr 2012 18:19:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747258#M2498</guid>
      <dc:creator>Jay_H_Intel</dc:creator>
      <dc:date>2012-04-30T18:19:53Z</dc:date>
    </item>
    <item>
      <title>Intel OMP_PROC_BIND implementation</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747259#M2499</link>
      <description>Thanks for taking the time to look into it.&lt;BR /&gt;&lt;BR /&gt;Petros</description>
      <pubDate>Mon, 30 Apr 2012 18:48:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747259#M2499</guid>
      <dc:creator>Petros</dc:creator>
      <dc:date>2012-04-30T18:48:29Z</dc:date>
    </item>
    <item>
      <title>Quote:jayhoeflinger wrote:</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747260#M2500</link>
      <description>&lt;BLOCKQUOTE&gt;jayhoeflinger wrote:&lt;BR /&gt;&lt;P&gt;Thanks for pointing out this problem. Wewill address this issue in an upcoming compiler release.&lt;BR /&gt;Regards,&lt;BR /&gt;Jay&lt;/P&gt;&lt;/BLOCKQUOTE&gt;

Just bumping the topic to say that the new 2013 Parallel Studio that rolled out didn't fix this...</description>
      <pubDate>Wed, 10 Oct 2012 09:07:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747260#M2500</guid>
      <dc:creator>Petros</dc:creator>
      <dc:date>2012-10-10T09:07:19Z</dc:date>
    </item>
    <item>
      <title>OMP_PROC_BIND is now fixed</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747261#M2501</link>
      <description>OMP_PROC_BIND is now fixed for compatible non-Intel processors in Intel® C++/Fortran Composer XE 2013  Update 1 and Intel® C++/Fortran Composer XE 2011  Update 13.  See &lt;A href="http://software.intel.com/en-us/articles/omp-proc-bind-is-now-supported-on-compatible-non-intel-processors" target="_blank"&gt;http://software.intel.com/en-us/articles/omp-proc-bind-is-now-supported-on-compatible-non-intel-processors&lt;/A&gt;
Patrick</description>
      <pubDate>Tue, 16 Oct 2012 21:15:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747261#M2501</guid>
      <dc:creator>pbkenned1</dc:creator>
      <dc:date>2012-10-16T21:15:13Z</dc:date>
    </item>
    <item>
      <title>Hi all,</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747262#M2502</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;I am also seeing a very large performance impact of thread migration when using a 6 and core CPU. The CPUs are 4960X and E5-2867W.&lt;/P&gt;
&lt;P&gt;I am attempting to solve that problem with the use of OMP_PROC_BIND.&amp;nbsp;However, I am having a problem with setting core affinity.&lt;/P&gt;
&lt;P&gt;My code is in FORTRAN and I am trying to use the OMP_GET_PROC_BIND and use a&amp;nbsp;call OMP_PROC_BIND(.TRUE.).&lt;/P&gt;
&lt;P&gt;I am using the ifort compiler. Version 11.1 Build 20100203 Package ID: w_cprof_p_11.1.060&lt;/P&gt;
&lt;P&gt;I compile the code with -Qopenmp but I get an error"unresolved external symbol _OMP_GET_PROC_BIND".&lt;/P&gt;
&lt;P&gt;All other openmp directives work; e.g. NTHREADS = OMP_GET_NUM_THREADS() etc.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2013 17:06:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747262#M2502</guid>
      <dc:creator>dfishman</dc:creator>
      <dc:date>2013-10-30T17:06:00Z</dc:date>
    </item>
    <item>
      <title>As the preceding reply</title>
      <link>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747263#M2503</link>
      <description>&lt;P&gt;As the preceding reply indicated, OpenMP 3.1 bits were still being introduced in the later 13.1 compiler updates (XE2013) so it would not be surprising that you must use the Intel proprietary equivalents KMP_AFFINITY to work with 11.1 compiler, if you didn't use the newer open sourced version of Intel OpenMP library.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2013 17:52:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Intel-OMP-PROC-BIND-implementation/m-p/747263#M2503</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2013-11-22T17:52:56Z</dc:date>
    </item>
  </channel>
</rss>

