<?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 i guess that's not in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160831#M27901</link>
    <description>&lt;P&gt;as i guess that's not possible because 32 bit version of library supports 32bit integer only and for cases exceed 2^31 there is only one chose - moving to the 64 bit version of mkl.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Mar 2019 03:42:02 GMT</pubDate>
    <dc:creator>Gennady_F_Intel</dc:creator>
    <dc:date>2019-03-01T03:42:02Z</dc:date>
    <item>
      <title>MKL Feast (inner memory problem: info=-2)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160828#M27898</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i'm trying to solve (sparse) symmetric generalized eigenvalue problems using dfeast_scrgv().&lt;/P&gt;&lt;P&gt;It always worked&amp;nbsp;fine with relatively small problems (up to 2000*2000 sparse matrix), but it turned out i can't solve the bigger ones (about 60000*60000 sparse matrix) as it always returns 'info = -2", that I know it refers to inner memory problems, but I don't know how to fix it.&lt;/P&gt;&lt;P&gt;The problem is solvable using other algorithms (not&amp;nbsp; included in&amp;nbsp;MKL).&lt;/P&gt;&lt;P&gt;I'm using the latest&amp;nbsp;Intel MKL 2019 library and&amp;nbsp;Intel C++ Compiler 19.0 on Visual Studio 2013 Platform Toolset.&lt;/P&gt;&lt;P&gt;May I ask you for some help?&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Daniele&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 15:08:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160828#M27898</guid>
      <dc:creator>Di_Luca__Daniele</dc:creator>
      <dc:date>2019-02-27T15:08:11Z</dc:date>
    </item>
    <item>
      <title>please try to use ILP64 API. </title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160829#M27899</link>
      <description>&lt;P&gt;please try to use ILP64 API.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 03:52:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160829#M27899</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2019-02-28T03:52:37Z</dc:date>
    </item>
    <item>
      <title>Thank you Gennady for the</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160830#M27900</link>
      <description>&lt;P&gt;Thank you Gennady for the support.&amp;nbsp;I'm sorry I forgot to write it before, but I need to compile a 32-bit project using that Feast routine, is there any other way to fix it besides running it in 64-bit, or is it a known issue? I can share the data I used if needed.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Daniele&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;Gennady F. (Intel) wrote:&lt;BR /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please try to use ILP64 API.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 08:19:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160830#M27900</guid>
      <dc:creator>Di_Luca__Daniele</dc:creator>
      <dc:date>2019-02-28T08:19:07Z</dc:date>
    </item>
    <item>
      <title>as i guess that's not</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160831#M27901</link>
      <description>&lt;P&gt;as i guess that's not possible because 32 bit version of library supports 32bit integer only and for cases exceed 2^31 there is only one chose - moving to the 64 bit version of mkl.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 03:42:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160831#M27901</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2019-03-01T03:42:02Z</dc:date>
    </item>
    <item>
      <title>Thank you Gennady,</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160832#M27902</link>
      <description>&lt;P style="margin-left:0cm; margin-right:0cm"&gt;Thank you&amp;nbsp;Gennady,&lt;/P&gt;&lt;P style="margin-left:0cm; margin-right:0cm"&gt;as you said, using the ILP64 API it works fine, though I had some problem setting the compiler (Intel C++ 19.0 on VS2017) to use the MKL 64bit libraries, and that’s why it needed so much to reply to you. Actually, I even opened a new topic&amp;nbsp;(&lt;A href="https://software.intel.com/en-us/forums/intel-math-kernel-library/topic/805556" style="color:#0563c1; text-decoration:underline"&gt;https://software.intel.com/en-us/forums/intel-math-kernel-library/topic/805556&lt;/A&gt;)&amp;nbsp;asking for help, as I went through some memory access violation&amp;nbsp;(which I still didn’t solve at all).&lt;/P&gt;&lt;P style="margin-left:0cm; margin-right:0cm"&gt;Thanks again,&lt;/P&gt;&lt;P style="margin-left:0cm; margin-right:0cm"&gt;Daniele&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 09:16:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Feast-inner-memory-problem-info-2/m-p/1160832#M27902</guid>
      <dc:creator>Di_Luca__Daniele</dc:creator>
      <dc:date>2019-03-05T09:16:30Z</dc:date>
    </item>
  </channel>
</rss>

