<?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 valgrind error in MPEG4 encoder in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912331#M14388</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;I am building a live transcoder using Intel IPP. It works pretty well, but when I run it with valgrind, I get some errorsand they all seem to relate to one particular subject. In summary the error report contains:&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000" size="2"&gt;Conditional jump or move depends on uninitialised value(s) at w7_ippiQuantIntra_MPEG4_16s_C1I &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000" size="2"&gt;Conditional jump or move depends on uninitialised value(s)at ippVideoEncoderMPEG4::TransMacroBlockIntra_MPEG4(unsigned char*, unsigned char*, unsigned char*, short*, int*, int, int, int, int*)by ippVideoEncoderMPEG4::EncodeIVOP() (ippvideoencodermpeg4_vop.cpp)&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;As far as I can see it, valgrind signals that coeffMB is unitialized, but using a memset on it does not remove the error. Removing the __ALIGN part of__ALIGN16(Ipp16s, coeffMB, 64*6); in EncodeIVOP() also does not change anything.&lt;/P&gt;
&lt;P&gt;It seems that ippiDCT8x8Fwd_8u16s_C1R or ippiQuantIntra_MPEG4_16s_C1I in TransMacroBlockIntra_MPEG4 do something with coeffMB (such that valgrind thinks the data is unitialized again) but since the IPP libraries are not built with debugging symbols and I do not have the source of IPP, I cannotlook into this code.&lt;/P&gt;
&lt;P&gt;It could be the case that valgrind (latestrelease 3.2.0)cannot handle this code, but when somebody knows more about this, please let me know.&lt;/P&gt;
&lt;P&gt;Greetings Werner.&lt;/P&gt;
&lt;P&gt;I do not get any memory leak errors, so that is ok :D.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Sep 2006 18:34:47 GMT</pubDate>
    <dc:creator>dierssen</dc:creator>
    <dc:date>2006-09-06T18:34:47Z</dc:date>
    <item>
      <title>valgrind error in MPEG4 encoder</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912331#M14388</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;I am building a live transcoder using Intel IPP. It works pretty well, but when I run it with valgrind, I get some errorsand they all seem to relate to one particular subject. In summary the error report contains:&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000" size="2"&gt;Conditional jump or move depends on uninitialised value(s) at w7_ippiQuantIntra_MPEG4_16s_C1I &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000" size="2"&gt;Conditional jump or move depends on uninitialised value(s)at ippVideoEncoderMPEG4::TransMacroBlockIntra_MPEG4(unsigned char*, unsigned char*, unsigned char*, short*, int*, int, int, int, int*)by ippVideoEncoderMPEG4::EncodeIVOP() (ippvideoencodermpeg4_vop.cpp)&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;As far as I can see it, valgrind signals that coeffMB is unitialized, but using a memset on it does not remove the error. Removing the __ALIGN part of__ALIGN16(Ipp16s, coeffMB, 64*6); in EncodeIVOP() also does not change anything.&lt;/P&gt;
&lt;P&gt;It seems that ippiDCT8x8Fwd_8u16s_C1R or ippiQuantIntra_MPEG4_16s_C1I in TransMacroBlockIntra_MPEG4 do something with coeffMB (such that valgrind thinks the data is unitialized again) but since the IPP libraries are not built with debugging symbols and I do not have the source of IPP, I cannotlook into this code.&lt;/P&gt;
&lt;P&gt;It could be the case that valgrind (latestrelease 3.2.0)cannot handle this code, but when somebody knows more about this, please let me know.&lt;/P&gt;
&lt;P&gt;Greetings Werner.&lt;/P&gt;
&lt;P&gt;I do not get any memory leak errors, so that is ok :D.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2006 18:34:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912331#M14388</guid>
      <dc:creator>dierssen</dc:creator>
      <dc:date>2006-09-06T18:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: valgrind error in MPEG4 encoder</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912332#M14389</link>
      <description>&lt;P&gt;Hello, thank you for your report. It seems that valgrind just do not handle all the things correctly. Did you try to check the code with some other tools?&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt; Vladimir&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2006 03:46:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912332#M14389</guid>
      <dc:creator>Vladimir_Dudnik</dc:creator>
      <dc:date>2006-09-15T03:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: valgrind error in MPEG4 encoder</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912333#M14390</link>
      <description>&lt;P&gt;Well, probably you are right. The error does not give me any problems, but I just wanted to check if there were more people with the same valgrind error :).&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2006 22:09:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/valgrind-error-in-MPEG4-encoder/m-p/912333#M14390</guid>
      <dc:creator>dierssen</dc:creator>
      <dc:date>2006-09-18T22:09:42Z</dc:date>
    </item>
  </channel>
</rss>

