<?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 Waterfall issue again on a deployed machine in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954042#M18855</link>
    <description>&lt;P&gt;Our project includes image processing function developped using IPP 7, and the project was packaged and then installed on a windows 7 x64 machine.&lt;/P&gt;
&lt;P&gt;Now, when the application program starts, it says "No DLL found for waterfall procedure"; We have searched the IPP document, and according to what it says, the ippi-X.X.dll has been included in the same folder as the executable file, and ippi.h is the only head file we used.&lt;/P&gt;
&lt;P&gt;3 dlls are in the application software folder: ippcore-7.0.dll, ippi-7.0.dll, and libiomp5md.dll, and I am certain that ippi-7.0.dll is the only dll file we used.&lt;/P&gt;
&lt;P&gt;I am wondering what we did wrong to cause this problem? Any thoughts/comments/hint?&lt;/P&gt;
&lt;P&gt;Thanks a&amp;nbsp; lot.&lt;/P&gt;
&lt;P&gt;Nick&lt;/P&gt;</description>
    <pubDate>Tue, 20 Nov 2012 20:08:39 GMT</pubDate>
    <dc:creator>Nick_T_1</dc:creator>
    <dc:date>2012-11-20T20:08:39Z</dc:date>
    <item>
      <title>Waterfall issue again on a deployed machine</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954042#M18855</link>
      <description>&lt;P&gt;Our project includes image processing function developped using IPP 7, and the project was packaged and then installed on a windows 7 x64 machine.&lt;/P&gt;
&lt;P&gt;Now, when the application program starts, it says "No DLL found for waterfall procedure"; We have searched the IPP document, and according to what it says, the ippi-X.X.dll has been included in the same folder as the executable file, and ippi.h is the only head file we used.&lt;/P&gt;
&lt;P&gt;3 dlls are in the application software folder: ippcore-7.0.dll, ippi-7.0.dll, and libiomp5md.dll, and I am certain that ippi-7.0.dll is the only dll file we used.&lt;/P&gt;
&lt;P&gt;I am wondering what we did wrong to cause this problem? Any thoughts/comments/hint?&lt;/P&gt;
&lt;P&gt;Thanks a&amp;nbsp; lot.&lt;/P&gt;
&lt;P&gt;Nick&lt;/P&gt;</description>
      <pubDate>Tue, 20 Nov 2012 20:08:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954042#M18855</guid>
      <dc:creator>Nick_T_1</dc:creator>
      <dc:date>2012-11-20T20:08:39Z</dc:date>
    </item>
    <item>
      <title>Hi Nick,</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954043#M18856</link>
      <description>Hi Nick, 
Besides the  ippcore-7.0.dll, ippi-7.0.dll, and libiomp5md.dll, you also need to put cpu-optimization dll like ippiv8.dll in the path where exe can find.  

Please see Understanding SIMD Optimization Layers and Dispatching in the Intel IPP 7.0 Library: http://software.intel.com/en-us/articles/understanding-simd-optimization-layers-and-dispatching-in-the-intel-ipp-70-library/


The DLLs like ippi-7.0.dll are "dispatcher" DLLs. At run time they will detect the processor and load the correct processor-specific DLLs. This allows your code to call Intel IPP functions without worrying about which processor the code will execute on - the appropriate version is automatically used. These processor-specific DLLs are named *w7*.dll, *v8*.dll  *p8".dll etc. . The only actions needed to use the Intel IPP DLLs, once the "stub" static libraries are linked, is to ensure that the dispatching DLLs and the processor-specific DLLs are on the path.

In general, the exe will search current folder, system32 folder, the folder of environment variable path points to to find the dlls at run-time. 
there are some solutions for these, for example,  
1) add IPP dll directory to system environment variable, thus exe can find it. 

Right click Icon"Computer" =&amp;gt; Open "System Properties"=&amp;gt; click Tab "Advanced"=&amp;gt;Environment Variables=&amp;gt; in System variables, click path =&amp;gt; Edit it. 
add C:\Program Files (x86)\Intel\Composer XE 2013\redist\ia32\ipp in Variable value. 
or  using the tools provided by IPP. 

set environment variable by ippenv.bat in a command-line windows and run exe after the setting. 
Open a command -line windows, run the bat files
&amp;gt; C:\Program Files (x86)\Intel\Composer XE 2013\ipp\bin\ippenv.bat"
then run your exe. 
&amp;gt; cd the directory of exe. 
&amp;gt;your.exe 

Best Regards,
Ying</description>
      <pubDate>Fri, 23 Nov 2012 02:15:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954043#M18856</guid>
      <dc:creator>Ying_H_Intel</dc:creator>
      <dc:date>2012-11-23T02:15:43Z</dc:date>
    </item>
    <item>
      <title>&gt;&gt;... I am certain that ippi</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954044#M18857</link>
      <description>&amp;gt;&amp;gt;... I am certain that ippi-7.0.dll is the only dll file we used...

That is not possible and CPU specific IPP DLLs must be used as well.</description>
      <pubDate>Fri, 23 Nov 2012 15:42:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954044#M18857</guid>
      <dc:creator>SergeyKostrov</dc:creator>
      <dc:date>2012-11-23T15:42:33Z</dc:date>
    </item>
    <item>
      <title>Quote:Ying H (Intel) wrote:</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954045#M18858</link>
      <description>&lt;BLOCKQUOTE&gt;Ying H (Intel) wrote:&lt;BR /&gt;&lt;P&gt;Hi Nick,&lt;BR /&gt;
Besides the  ippcore-7.0.dll, ippi-7.0.dll, and libiomp5md.dll, you also need to put cpu-optimization dll like ippiv8.dll in the path where exe can find.  &lt;/P&gt;
&lt;P&gt;Please see Understanding SIMD Optimization Layers and Dispatching in the Intel IPP 7.0 Library: &lt;A href="http://software.intel.com/en-us/articles/understanding-simd-optimization-layers-and-dispatching-in-the-intel-ipp-70-library/"&gt;http://software.intel.com/en-us/articles/understanding-simd-optimization...&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The DLLs like ippi-7.0.dll are "dispatcher" DLLs. At run time they will detect the processor and load the correct processor-specific DLLs. This allows your code to call Intel IPP functions without worrying about which processor the code will execute on - the appropriate version is automatically used. These processor-specific DLLs are named *w7*.dll, *v8*.dll  *p8".dll etc. . The only actions needed to use the Intel IPP DLLs, once the "stub" static libraries are linked, is to ensure that the dispatching DLLs and the processor-specific DLLs are on the path.&lt;/P&gt;
&lt;P&gt;In general, the exe will search current folder, system32 folder, the folder of environment variable path points to to find the dlls at run-time.&lt;BR /&gt;
there are some solutions for these, for example,&lt;BR /&gt;
1) add IPP dll directory to system environment variable, thus exe can find it. &lt;/P&gt;
&lt;P&gt;Right click Icon"Computer" =&amp;gt; Open "System Properties"=&amp;gt; click Tab "Advanced"=&amp;gt;Environment Variables=&amp;gt; in System variables, click path =&amp;gt; Edit it.&lt;BR /&gt;
add C:\Program Files (x86)\Intel\Composer XE 2013\redist\ia32\ipp in Variable value.&lt;BR /&gt;
or  using the tools provided by IPP. &lt;/P&gt;
&lt;P&gt;set environment variable by ippenv.bat in a command-line windows and run exe after the setting.&lt;BR /&gt;
Open a command -line windows, run the bat files&lt;BR /&gt;
&amp;gt; C:\Program Files (x86)\Intel\Composer XE 2013\ipp\bin\ippenv.bat"&lt;BR /&gt;
then run your exe.&lt;BR /&gt;
&amp;gt; cd the directory of exe.&lt;BR /&gt;
&amp;gt;your.exe &lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;
Ying &lt;/P&gt;&lt;/BLOCKQUOTE&gt;

Hi Ying:
You are absolutely right, and your explanation is very detail and clear. Thanks a lot!!</description>
      <pubDate>Mon, 26 Nov 2012 14:21:44 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954045#M18858</guid>
      <dc:creator>Nick_T_1</dc:creator>
      <dc:date>2012-11-26T14:21:44Z</dc:date>
    </item>
    <item>
      <title>Quote:Sergey Kostrov wrote:</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954046#M18859</link>
      <description>&lt;BLOCKQUOTE&gt;Sergey Kostrov wrote:&lt;BR /&gt;&lt;P&gt;&amp;gt;&amp;gt;... I am certain that ippi-7.0.dll is the only dll file we used...&lt;/P&gt;
&lt;P&gt;That is not possible and CPU specific IPP DLLs must be used as well.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;

Thanks.</description>
      <pubDate>Mon, 26 Nov 2012 14:22:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/Waterfall-issue-again-on-a-deployed-machine/m-p/954046#M18859</guid>
      <dc:creator>Nick_T_1</dc:creator>
      <dc:date>2012-11-26T14:22:37Z</dc:date>
    </item>
  </channel>
</rss>

