<?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 MKL Sparse BLAS: different MKL_INT types?  in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Sparse-BLAS-different-MKL-INT-types/m-p/928619#M13552</link>
    <description>Hi, these are interesting questions. Please give me a little time to research it with the MKL engineering team. I'd like to get a definitive answer on the feasibility of #2. It may help me with a great answer to question #1.</description>
    <pubDate>Wed, 29 Aug 2012 19:10:18 GMT</pubDate>
    <dc:creator>Noah_C_Intel</dc:creator>
    <dc:date>2012-08-29T19:10:18Z</dc:date>
    <item>
      <title>MKL Sparse BLAS: different MKL_INT types?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Sparse-BLAS-different-MKL-INT-types/m-p/928618#M13551</link>
      <description>&lt;P&gt;On my platform, the MKL_INT macro must yield an integral type that is binary-compatible with a 32-bit signed int, or 64-bit signed int if I link with the ILP64 libraries [&lt;A href="http://redfort-software.intel.com/sites/products/documentation/hpc/mkl/lin/MKL_UG_structure/Support_for_ILP64_Programming.htm"&gt;MKL doc&lt;/A&gt;]&amp;nbsp;&lt;SPAN style="font-family: Verdana, Arial, Helvetica, sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt; 1) Is there a way to call into both the LP64 and ILP64 versions of MKL Sparse BLAS routines like&amp;nbsp;mkl_dcsrmv(), from the &lt;I&gt;same&lt;/I&gt; C++ program? &lt;BR /&gt; 2) In future releases, would the MKL developers consider allowing users to&amp;nbsp;&lt;I&gt;redefine&lt;/I&gt; MKL_INT to different integral types? In my use-case, I have many small sparse matrices whose indices can be represented by 8- and 16-bit integers, so there's potential 2-to-8-fold memory footprint savings (w.r.t. indexing data) versus using the MKL defaults.Thanks! --Nick&lt;/P&gt;</description>
      <pubDate>Wed, 29 Aug 2012 18:38:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Sparse-BLAS-different-MKL-INT-types/m-p/928618#M13551</guid>
      <dc:creator>Nicholas_K_2</dc:creator>
      <dc:date>2012-08-29T18:38:24Z</dc:date>
    </item>
    <item>
      <title>MKL Sparse BLAS: different MKL_INT types?</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Sparse-BLAS-different-MKL-INT-types/m-p/928619#M13552</link>
      <description>Hi, these are interesting questions. Please give me a little time to research it with the MKL engineering team. I'd like to get a definitive answer on the feasibility of #2. It may help me with a great answer to question #1.</description>
      <pubDate>Wed, 29 Aug 2012 19:10:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/MKL-Sparse-BLAS-different-MKL-INT-types/m-p/928619#M13552</guid>
      <dc:creator>Noah_C_Intel</dc:creator>
      <dc:date>2012-08-29T19:10:18Z</dc:date>
    </item>
  </channel>
</rss>

