<?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 heap corruption on cblas_sgemv in release mode in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785761#M1844</link>
    <description>I've found the issue.&lt;DIV&gt;I was linking in release mode with different libs than in debug.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Building was ok though with no warnings or complaints on unresolved symbols.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Everything is Ok now, no pb in cblas functions in my code.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 13 Jul 2012 07:38:11 GMT</pubDate>
    <dc:creator>Bruno_Colombet</dc:creator>
    <dc:date>2012-07-13T07:38:11Z</dc:date>
    <item>
      <title>heap corruption on cblas_sgemv in release mode</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785759#M1842</link>
      <description>&lt;P&gt;Hello everyone,I'm just using MKL for two weeks and I face a strange behavior.My code is running fine in DEBUG but crash in Release. Ok it's a well known pb, but I've checked all macros and coding problem and can't see the light.Here is the function causing the crash on cblas_sgemv, it seems..[cpp]void randperm(float *data, float *trsf, float *bias, int *perm, int m, int n, int k, float *proj) { int i, im, swap, inc = 1; float alpha = 1.0, beta; if (bias) { for (i=0,im=0 ; iperm is allocated before and its size is k elements.data is allocated before and its size is m x n elements.I had a similar behavior in another function in which I was using sgesv_().I replaced with a LAPACKE call : LAPACKE_sgesv() and problem was solved.I know heap corruption are not easy to detect but I'm wondering where is exaclty the heap corruption...Any idea will be appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jul 2012 14:51:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785759#M1842</guid>
      <dc:creator>Bruno_Colombet</dc:creator>
      <dc:date>2012-07-11T14:51:15Z</dc:date>
    </item>
    <item>
      <title>heap corruption on cblas_sgemv in release mode</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785760#M1843</link>
      <description>Bruno, can you give the comprehensive example to check on our side?</description>
      <pubDate>Fri, 13 Jul 2012 00:57:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785760#M1843</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2012-07-13T00:57:24Z</dc:date>
    </item>
    <item>
      <title>heap corruption on cblas_sgemv in release mode</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785761#M1844</link>
      <description>I've found the issue.&lt;DIV&gt;I was linking in release mode with different libs than in debug.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Building was ok though with no warnings or complaints on unresolved symbols.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Everything is Ok now, no pb in cblas functions in my code.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 13 Jul 2012 07:38:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/heap-corruption-on-cblas-sgemv-in-release-mode/m-p/785761#M1844</guid>
      <dc:creator>Bruno_Colombet</dc:creator>
      <dc:date>2012-07-13T07:38:11Z</dc:date>
    </item>
  </channel>
</rss>

