<?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 Re: Possible Bug in oneMKL 2025.3 in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746509#M37556</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for posting in the forum!&lt;/P&gt;
&lt;P&gt;For the 2D complex case, I didn't manage to reproduce it. Could you show more details how it was built?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;For the 2D real case, &lt;A href="https://www.intel.com/content/www/us/en/docs/onemkl/developer-reference-c/2025-2/dfti-input-strides-dfti-output-strides.html#:~:text=Note%20that%20in,explicitly%2C%20as%20follows%3A" target="_self"&gt;strides need to be set explicitly&lt;/A&gt;. After setting both strides, the code runs with no error.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Fengrui&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 01 May 2026 19:37:03 GMT</pubDate>
    <dc:creator>Fengrui</dc:creator>
    <dc:date>2026-05-01T19:37:03Z</dc:date>
    <item>
      <title>Possible Bug in oneMKL 2025.3</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746320#M37555</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have found a possible bug in oneMKL version 2025.3 using VS 2026. Please let me know, if you need any further information.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Version:&lt;/P&gt;&lt;P&gt;Intel(R) oneAPI Math Kernel Library Version 2025.3-Product Build 20251007 for Intel(R) 64 architecture applications&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Building for x64 on Windows,&amp;nbsp;MKL_ILP64 is _not_ defined.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The test (see code below) gives:&lt;/P&gt;&lt;PRE&gt;1D real create -&amp;gt; status=0, msg=Intel oneMKL DFTI SUCCESS: No error
1D real commit -&amp;gt; status=0, msg=Intel oneMKL DFTI SUCCESS: No error
2D complex create -&amp;gt; status=0, msg=Intel oneMKL DFTI SUCCESS: No error
2D complex commit -&amp;gt; status=9, msg=Intel oneMKL DFTI ERROR: Transforms with number of points N of a non-unit stride dimension exceeding 2^(27-p) - 1 for N a power-of-two, or 2^(23-p) - 1 for N not a power-of-two, are currently not supported, where p=0 for single precision and p=1 for double precision
2D real create -&amp;gt; status=0, msg=Intel oneMKL DFTI SUCCESS: No error
2D real commit -&amp;gt; status=3, msg=Intel oneMKL DFTI ERROR: Inconsistent configuration parameters&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Code:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;static void DebugOut(const char* text)
{
    OutputDebugStringA(text);
}

static void DebugStatus(const char* name, MKL_LONG status)
{
    char buffer[1024];
    _snprintf_s(
        buffer,
        sizeof(buffer),
        _TRUNCATE,
        "%s -&amp;gt; status=%ld, msg=%s\n",
        name,
        status,
        DftiErrorMessage(status));

    OutputDebugStringA(buffer);
}

static void TestDftiMinimal()
{
    MKL_LONG status = 0;
    DFTI_DESCRIPTOR_HANDLE h = nullptr;

    {
        status = DftiCreateDescriptor(&amp;amp;h, DFTI_SINGLE, DFTI_REAL, 1, (MKL_LONG)16);
        DebugStatus("1D real create", status);
        if (status == DFTI_NO_ERROR)
        {
            status = DftiCommitDescriptor(h);
            DebugStatus("1D real commit", status);
            DftiFreeDescriptor(&amp;amp;h);
        }
    }

    {
        MKL_LONG dims[2] = { 16, 16 };
        status = DftiCreateDescriptor(&amp;amp;h, DFTI_SINGLE, DFTI_COMPLEX, 2, dims);
        DebugStatus("2D complex create", status);
        if (status == DFTI_NO_ERROR)
        {
            status = DftiCommitDescriptor(h);
            DebugStatus("2D complex commit", status);
            DftiFreeDescriptor(&amp;amp;h);
        }
    }

    {
        MKL_LONG dims[2] = { 16, 16 };
        status = DftiCreateDescriptor(&amp;amp;h, DFTI_SINGLE, DFTI_REAL, 2, dims);
        DebugStatus("2D real create", status);
        if (status == DFTI_NO_ERROR)
        {
            status = DftiCommitDescriptor(h);
            DebugStatus("2D real commit", status);
            DftiFreeDescriptor(&amp;amp;h);
        }
    }
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 06:56:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746320#M37555</guid>
      <dc:creator>JörgZeiner</dc:creator>
      <dc:date>2026-04-30T06:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: Possible Bug in oneMKL 2025.3</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746509#M37556</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for posting in the forum!&lt;/P&gt;
&lt;P&gt;For the 2D complex case, I didn't manage to reproduce it. Could you show more details how it was built?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;For the 2D real case, &lt;A href="https://www.intel.com/content/www/us/en/docs/onemkl/developer-reference-c/2025-2/dfti-input-strides-dfti-output-strides.html#:~:text=Note%20that%20in,explicitly%2C%20as%20follows%3A" target="_self"&gt;strides need to be set explicitly&lt;/A&gt;. After setting both strides, the code runs with no error.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Fengrui&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 May 2026 19:37:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746509#M37556</guid>
      <dc:creator>Fengrui</dc:creator>
      <dc:date>2026-05-01T19:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: Possible Bug in oneMKL 2025.3</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746694#M37566</link>
      <description>&lt;P&gt;Thanks Fengrui,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I solved the problem. I had mkl_intel_ilp64.lib instead of&amp;nbsp;mkl_intel_lp64.lib in AdditionalDependencies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jörg&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2026 14:15:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Possible-Bug-in-oneMKL-2025-3/m-p/1746694#M37566</guid>
      <dc:creator>JörgZeiner</dc:creator>
      <dc:date>2026-05-04T14:15:46Z</dc:date>
    </item>
  </channel>
</rss>

