<?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 Thanks! Any update on this? in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165215#M28188</link>
    <description>&lt;P&gt;Thanks! Any update on this?&lt;/P&gt;</description>
    <pubDate>Thu, 26 Apr 2018 02:04:55 GMT</pubDate>
    <dc:creator>ydl</dc:creator>
    <dc:date>2018-04-26T02:04:55Z</dc:date>
    <item>
      <title>Access violation in mkl_set_interface_layer with Python 3</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165211#M28184</link>
      <description>&lt;P&gt;Using mkl_set_interface_layer from Python 3 on Windows 10 with the latest MKL installed gives an access violation. Specifically this code:&lt;/P&gt;

&lt;PRE class="brush:python;"&gt;from ctypes import *
mkl = cdll.LoadLibrary('mkl_rt')
mkl.mkl_set_interface_layer(c_int(1))&lt;/PRE&gt;

&lt;P&gt;produces this error:&lt;/P&gt;

&lt;PRE class="brush:plain;"&gt;OSError: exception: access violation reading 0x0000000000000001&lt;/PRE&gt;

&lt;P&gt;Note using c_int(0) in place of c_int(1) gives an analogous error. Variables in the console are set using mklvars.bat (notably the PATH variables are set properly), and I have checked that several of the cblas_* functions are working. Is there some library I have to load, or specify a calling convention?&lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Apr 2018 22:02:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165211#M28184</guid>
      <dc:creator>ydl</dc:creator>
      <dc:date>2018-04-05T22:02:01Z</dc:date>
    </item>
    <item>
      <title>&gt;&gt; the latest MKL -- do you</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165212#M28185</link>
      <description>&lt;P&gt;&amp;gt;&amp;gt; the latest MKL -- do you mean MKL v. 2018 u2?&amp;nbsp; please quick check mkl_version.h header to take this info.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Apr 2018 03:55:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165212#M28185</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2018-04-06T03:55:57Z</dc:date>
    </item>
    <item>
      <title>Yes, I mean that one.</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165213#M28186</link>
      <description>&lt;P&gt;Yes, I mean that one. Specifically, I have, in mkl_version.h,&lt;/P&gt;

&lt;PRE class="brush:cpp;"&gt;#define __INTEL_MKL_BUILD_DATE 20180128

#define __INTEL_MKL__ 2018
#define __INTEL_MKL_MINOR__ 0
#define __INTEL_MKL_UPDATE__ 2

#define INTEL_MKL_VERSION 20180002&lt;/PRE&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Apr 2018 04:25:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165213#M28186</guid>
      <dc:creator>ydl</dc:creator>
      <dc:date>2018-04-06T04:25:20Z</dc:date>
    </item>
    <item>
      <title>yes, we confirmed the problem</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165214#M28187</link>
      <description>&lt;P&gt;yes, we confirmed the problem on our side and will work on this issue. We will keep you posted.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2018 03:26:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165214#M28187</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2018-04-09T03:26:53Z</dc:date>
    </item>
    <item>
      <title>Thanks! Any update on this?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165215#M28188</link>
      <description>&lt;P&gt;Thanks! Any update on this?&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 02:04:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Access-violation-in-mkl-set-interface-layer-with-Python-3/m-p/1165215#M28188</guid>
      <dc:creator>ydl</dc:creator>
      <dc:date>2018-04-26T02:04:55Z</dc:date>
    </item>
  </channel>
</rss>

