Intel Software Network articles Feed http://software.intel.com/en-us/articles/intel-parallel-composer-kb/type/software-defects/ en-us "The system cannot find the path specified" when building samples using Intel® Threading Building Blocks
Reference Number : DPD200172472


Version : 2011


Product : Intel® C++ Composer XE, Intel® Parallel Composer


Operating System : Windows*


Problem Description : In update 6, certain compiler samples that use Intel® Threading Building Blocks, for example cilk\qsort-mutex may fail when built in Microsoft Visual Studio 2010* during a post-build copy step.  The output you get will look like:

1>  Description: Copy TBB DLLs
1>  The system cannot find the path specified.
1>  The system cannot find the path specified.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: The command "copy /y "\redist\ia32\tbb\vc_mt\tbb_debug.dll" "C:\Cilk\RC3\Cilk\qsort-mutex\Debug\"
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: copy /y "\redist\ia32\tbb\vc_mt\tbbmalloc_debug.dll" "C:\Cilk\RC3\Cilk\qsort-mutex\Debug\"
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: 
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: :VCEnd" exited with code 1.
1>
1>Build FAILED.

Resolution Status : We are working on resolving this in a future release.  In the meantime, go to the project properties for the sample in question, go to "Build Events->Post Build Event" and Edit the "Command Line" field, and replace any instance of "$(INTEL_DEF_IA32_INSTALL_DIR)" with the hardcoded path to the Intel Parallel Composer or C++ Composer XE root directory.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/the-system-cannot-find-the-path-specified-when-building-samples-using-intel-threading-building-blocks/ Tue, 06 Sep 2011 00:00:00 -0700 http://software.intel.com/en-us/articles/the-system-cannot-find-the-path-specified-when-building-samples-using-intel-threading-building-blocks/#comments http://software.intel.com/en-us/articles/the-system-cannot-find-the-path-specified-when-building-samples-using-intel-threading-building-blocks/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Function maps in Array Notation are not converted to multi-threaded calls
Reference Number : DPD200167322


Version : 12.0


Product : Intel® C++ Compiler XE


Operating System : Windows*, Linux* and Mac* OS


Problem Description : 
In "Intel® C++ Compiler XE 12.0 User and Reference Guides" -> "Creating Parallel Applications" -> "Using Intel(R) Cilk(TM) Plus" -> "Extensions for Array Notation" -> "C/C++ Extensions for Array Notations Programming Model", it says:

"Function maps are powerful tools used to apply a set of operations in parallel to all elements of an array section. The compiler takes advantage of function maps to generate multi-threaded parallel calls."

At this point, Intel C++ Compiler XE doesn't generate multi-threaded code for function maps. The last sentence needs to be removed.


Resolution Status : 
This documentation defect has been fixed. The fix will be available in a future product update.


[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/function-maps-in-array-notation-are-not-converted-to-multi-threaded-calls/ Mon, 27 Jun 2011 08:00:00 -0700 http://software.intel.com/en-us/articles/function-maps-in-array-notation-are-not-converted-to-multi-threaded-calls/#comments http://software.intel.com/en-us/articles/function-maps-in-array-notation-are-not-converted-to-multi-threaded-calls/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base internal error: 0_1204 when openmp used with try-catch
Reference Number : Q625172


Version : 12.0 update 1 & 2


Product : Intel® C++ Compiler XE 12.0 update 1 & 2


Operating System : Windows*


Problem Description : 
The below code was reduced from a big customer project, that uses Qt. The bug is in Intel compiler,
when openmp pragma/option is used, and exception-handling is used in a particular manner, though not in other cases. The workaround is to use /Od , instead of /O2. Or, do not use openmp pragma. Also, enable /EHsc since C++ exception handling mechanism is used.

Command-line for the bug:--
icl /c /Qopenmp /EHsc qterror.cpp

compile Error :-- internal error: 0_1204

Sometimes, during parallel compilation (using /MP), when such compile errors are generated, the below error message also comes in the output.
icl: error #10298: problem during post processing of parallel object compilation

Below sample code generates the error:--

#include <iostream>
using namespace std;
#include <vector>

class myclass{};
vector<myclass>					myvec;
template <typename T>
const T &mymin(const T &a, const T &b) { if (a < b) return a; return b; }
void func(const char* ch, const char* FILE, int LINE)
{
	cout << ch << " in file: " << __FILE__ << " in line: " << __LINE__ << "\n";
	return;
}
bool Do()
	{
		myclass *j=&myvec[100];
		int lines = mymin(10,100);

		if(!lines)
		{
			{
			#pragma omp parallel for //num_threads(komp_num_threads) schedule(guided)
			for (int y = 0; y <= 100; y++)
			{
			try {
			func( "Openmp error",__FILE__, __LINE__ );		
				
			}catch(std::exception e) { };
			}
		}
		}
		
		return 1;
}


Resolution Status : This bug has been resolved in Intel Composer 12.0 XE update 3 , 4



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/internal-error-0_1204-when-openmp-used-with-try-catch/ Tue, 07 Jun 2011 08:30:00 -0700 http://software.intel.com/en-us/articles/internal-error-0_1204-when-openmp-used-with-try-catch/#comments http://software.intel.com/en-us/articles/internal-error-0_1204-when-openmp-used-with-try-catch/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base mathimf.h is incompatible with system math.h Reference number: DPD200166165

Problem : mathimf.h problem in VS2010

Environment : VS2010 , Intel C++ compiler

Affected compilers: 12.0 u/d (1 to 4)

Sample code: 

#pragma once

#include <string>
using std::string;

#include <mathimf.h>

class bccb
{
bccb(void);
~bccb(void);
};


bccb::bccb(void)
{
}

bccb::~bccb(void)
{
}

Problem Description:--
When above is compiled with Intel compiler in VS2010 mode, following error:--

# error "<mathimf.h> is incompatible with system <math.h>!"

With VS2008, the code compiles fine.

Solutions/workarounds:--

1. Use math.h instead of mathimf.h, and in case of a needed Intel-specific functions, their definitions can be taken from mathimf.h and inserted into application code.

2. Standard recommendation is to avoid usage of math.h and mathimf.h in the same compilation unit
by separating code that depends on math.h from the code that depends on mathimf.h into dirrerent files.
The above code though has the problem that the use is not avoided. This is an issue needed to be fixed.

3. First, try to include <mathimf.h> before any other header. This will automatically prevent futher inclusions of <math.h>.
So, include <mathimf.h before <string> . But still icl in VS2010 mode does not compile, and this will be fixed in later release. <math.h> should never be mistakenly used before <mathimf.h>, as this would definitely cause problems due to below reason:--

In C language,
MS math.h deprecates usage of some c99-functions.
The issue here is that MS does not support ISO C99.
Also a number of float and long double functions are defined
through calls to corresponding double-precision functions,
giving performance or accuracy loss compared to float/long-double functions
existing in Intel math library.

In C++ language,
MS redefines a number of c99-functions so that they are inlined.

Resolution status:
This issue will be fixed in the later 12.0 release and next major release 12.1.
So, including <mathimf.h> before <math.h> explicitly or inadvertently as in sample code will build fine with VS2010 in later 12.x .

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]



]]> http://software.intel.com/en-us/articles/mathimf-is-incompatible-with-system-math/ Mon, 30 May 2011 08:30:00 -0700 http://software.intel.com/en-us/articles/mathimf-is-incompatible-with-system-math/#comments http://software.intel.com/en-us/articles/mathimf-is-incompatible-with-system-math/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base How to prevent source code full path location information from being visible in an executable
Problem : When using the -openmp  or -parallel compiler options under linux* or Mac OS* X, or the /Qopenmp or /Qparallel options under Windows, the resulting executable files contain the full pathnames to the source files for each source file containing an OpenMP or Parallel region.   This was done to allow Intel profiling and correctness checking tools to be able to find and display source information in the analysis tools.


Environment : Windows*, Linux*, Mac OS* X, all compilers since 9.1 versions

Root Cause :
The Intel compilers by default included source file full path information so that Intel analysis tools could find source files during analysis for correctness or performance.

Resolution :
With the release of Intel Composer XE ( aka version 12.0 ) an option was included to allow removing this source path information from the executable header information:

Linux and Mac OS X:   -no-parallel-source-info  compiler option should be used
Windows:     /Qparallel-source-info-   compiler option should be used

These options are only available in the 12.0 aka Composer XE compiler products.  If you are using an older version, please upgrade to 12.0.

]]> http://software.intel.com/en-us/articles/how-to-prevent-source-code-full-path-location-information-from-being-visible-in-an-executable/ Thu, 16 Dec 2010 20:00:00 -0800 http://software.intel.com/en-us/articles/how-to-prevent-source-code-full-path-location-information-from-being-visible-in-an-executable/#comments http://software.intel.com/en-us/articles/how-to-prevent-source-code-full-path-location-information-from-being-visible-in-an-executable/ Intel® Parallel Composer Intel® Cluster Toolkit Compiler Intel® Compilers Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Cluster Toolkit for Linux* Knowledge Base Intel® Cluster Toolkit for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Parallel Composer Knowledge Base Floating-point Settings in Worker Threads May Differ from Master Thread for OpenMP, TBB and Intel Cilk Plus
Reference Number : dpd20087206, bz-1755, dpd20088154


Version : 2011 (Compiler 12.0)


Product : Intel Parallel Composer and Intel Composer XE


Operating System : Windows, Linux, Mac OS X


Problem Description : 
On most operating systems, thread-creation routines do not propagate the floating-point state from the master thread to worker threads. Consequently, settings such as the rounding mode or abrupt underflow, (also known as flush-to-zero), may differ in the worker threads. It is therefore possible that a computation performed in a worker thread may not get the identical result to a similar computation carried out in the master thread. This may occur for applications built with the Intel Compiler version 12 that use either OpenMP or Intel Cilk Plus, or for applications that use Intel Threading Building Blocks (TBB), built with any Intel or other compiler, such as gcc.

For example, if an application is compiled on Windows with /O2 /Qopenmp, abrupt underflow would be enabled for the master thread but not for the workers, and a floating-point operation that resulted in a denormalized number for a worker thread would result in zero for the master thread. If a Fortran application was compiled with /Qopenmp /fpe:0, or a C application with /Qopenmp /Qfp-trap:common, to unmask floating-point exceptions, a division by zero occurring in the master thread would raise an exception, but one occurring in the worker thread would not. See the Intel Compiler User and Reference Guide for other switches that might modify the floating-point control word.


Resolution Status : 
For OpenMP, this issue may be worked around by setting the environment variable KMP_INHERIT_FP_CONTROL=1. This will cause the worker threads to inherit the floating-point settings of the master thread at the time of thread creation. This setting has been made the default in the 12.0 compiler update 2 contained in Intel Composer XE 2011 update 2.

For Intel Cilk Plus, the floating-point state could be set explicitly for each thread. The issue will be addressed in a future compiler update.
For TBB, the issue has been fixed in TBB version 3.0 update 5 and in Intel C++ Composer XE 2011 update 2.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/floating-point-settings-in-worker-threads-may-differ-from-master-thread-for-openmp-tbb-and-intel-cilk-plus/ Wed, 08 Dec 2010 00:00:00 -0800 http://software.intel.com/en-us/articles/floating-point-settings-in-worker-threads-may-differ-from-master-thread-for-openmp-tbb-and-intel-cilk-plus/#comments http://software.intel.com/en-us/articles/floating-point-settings-in-worker-threads-may-differ-from-master-thread-for-openmp-tbb-and-intel-cilk-plus/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Fortran Compiler for Linux* Knowledge Base Intel® Fortran Compiler for Mac OS X* Knowledge Base Intel® Parallel Composer Knowledge Base Intel® Threading Building Blocks Knowledge Base Intel® Visual Fortran Compiler for Windows* Knowledge Base Error: Command line error at &#39;source&#39; upon uninstalling Intel(R) Parallel Composer 2011
Reference Number : DPD200160534 


Version : 2011


Product : Intel(R) Parallel Composer 2011


Operating System : Windows 7*, Windows XP*, Windows Server 2003*


Problem Description : The following error is displayed when you try to uninstall Intel(R) Parallel Composer 2011 from Add/Remove Programs:
      "Intel(R) Composer 2011 for Windows* installation.  Copyright(c) 2010, Intel Corporation.  All Rights reserved.
             Error: Command line error at 'source'.  Installation will end.  Suggestion: Use '--help' for assistance."

The problem could possibly occur when multiple versions of the Intel(R) Parllel Composer, Intel(R) Parallel Studio, and IntelR) C++ Compiler 11.1 are installed on the same system, and partially uninstalled.  For example, one scenario where this problem has been seen is:

1- Install Parallel Studio 2011 

2- Install Intel C++ Compiler Professional V11.1 update 5, and select not to install IDE integration. 

3- Install newer version of Parallel Composer 2011

4- An attempt to uninstall Parallel Composer could lead to the error described above


Resolution Status : This may be resolved in a future product update.  The following workaround may help resolving the problem:

1. Invoke C:\Program files (x86)\intel\Parallel Studio 2011\Composer\setup_c\setup.exe     OR
               C:\Program files (x86)\intel\Parallel Composer 2011\Composer\setup_c\setup.exe    


2. Select "Remove" and follow the instructions to uninstall the product




[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/error-command-line-error-at-source-upon-uninstalling-intelr-parallel-composer-2011/ Wed, 29 Sep 2010 21:00:00 -0700 http://software.intel.com/en-us/articles/error-command-line-error-at-source-upon-uninstalling-intelr-parallel-composer-2011/#comments http://software.intel.com/en-us/articles/error-command-line-error-at-source-upon-uninstalling-intelr-parallel-composer-2011/ Intel® Parallel Composer Knowledge Base Backend Signals error when compiling code including Intel® Cilk™ Plus headers Reference Number : DPD200159529


Version : 2011


Product : Intel® Parallel Composer


Operating System : Windows*


Problem Description : When compiling multiple files in a Visual C++ project with the Intel(R) C++ Compiler or compiling multiple files on one command line, you may see a backend signals internal error if the files are using Intel® Cilk™ Plus header files.  You can confirm this issue applies to you if you can compile any one source file without seeing the backend signals error.


Resolution Status : Our developers are working towards a fix for this issue.  If a workaround is needed, please contact us via User Forum or Intel® Premier Support.  This issue does not exist in the Intel® C++ Composer XE.



[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.] ]]> http://software.intel.com/en-us/articles/backend-signals-error-when-compiling-code-including-intel-cilk-plus-headers/ Wed, 01 Sep 2010 21:00:00 -0700 http://software.intel.com/en-us/articles/backend-signals-error-when-compiling-code-including-intel-cilk-plus-headers/#comments http://software.intel.com/en-us/articles/backend-signals-error-when-compiling-code-including-intel-cilk-plus-headers/ Intel® Parallel Composer Knowledge Base Invalid &#34;error #2593: calls to non-vector function are not supported in vector function&#34; at /Od or /O1
Reference Number : DPD200158944


Version : 2011


Product : Intel® Parallel Composer


Operating System : Windows*


Problem Description : If an elemental function with the attribute __declspec(vector) contains a call to a math function like sqrt, you may get an error at compile time when using /Od or /O1:

error #2593: calls to non-vector function are not supported in vector function


Resolution Status : Some issues are resolved in update 3 of both Intel Parallel Composer 2011 and Composer XE 2011.  Others are resolved in update 9 of both products.


[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/invalid-error-2593-calls-to-non-vector-function-are-not-supported-in-vector-function-at-od-or-o1/ Wed, 01 Sep 2010 00:00:00 -0700 http://software.intel.com/en-us/articles/invalid-error-2593-calls-to-non-vector-function-are-not-supported-in-vector-function-at-od-or-o1/#comments http://software.intel.com/en-us/articles/invalid-error-2593-calls-to-non-vector-function-are-not-supported-in-vector-function-at-od-or-o1/ Intel® C++ Compiler for Windows* Knowledge Base Intel® Parallel Composer Knowledge Base Compressed data generated by ipp-zlib cannot be decompressed
Reference Number : DPD200151952

Version :  6.1 update 4 or older versions

Product : Intel® Integrated Performance Primitives (Intel® IPP) 

Operating System :  Linux*, Windows* and Mac* OS

Problem Description :  When a buffer size is equal to a default buffer size (32Kb)  used in open source zlib  or with any other buffer sizes that are equal to the power of 2, the Intel IPP zlib works correctly.   But when the compression is called repeatedly with non-default buffer size (for example in range (32Kb-258)->(32Kb-1)), the compressed data generated by the Intel IPP-zlib cannot be decompressed by either the Intel IPP-zlib or the open-source zlib.

Resolution Status : This issue is fixed in Intel IPP v6.1 update 5, please go to Intel Registration Center to get software upgrade.

This issue is fixed in "deflate.c" file  which is included in "..\data-compression\ipp_zlib\src" from Intel IPP sample package,  there is no impact on the Intel IPP API level.

Updates on May 3, 2010: We discovered another potential data compression error (reference number DPD200154198
 ) when the buffer size = 64K based in version 6.1 update 5.  The modified code has been added into the "deflate.c" source file (see "Article Attachments" below). 

If you want to upgrade to this latest modified "deflate.c" source file, please follow these steps:
1. Install the latest Intel IPP sample packages from v6.1 update 5
2. Replace the the "deflate.c" included in the Intel IPP sample directory "..\data-compression\ipp_zlib\src" with the newest file (see "Article Attachments" below)
3. Rebulid the ipp-zlib sample to generate a new ipp-zlib library.

If you still find issues regard data compression errors, please report us with complete test case via Intel IPP forum or Intel Premier Support channel.

We will include this fix in the next Intel IPP release update.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
]]> http://software.intel.com/en-us/articles/ipp-zlib-compression-error/ Thu, 08 Apr 2010 21:00:00 -0700 http://software.intel.com/en-us/articles/ipp-zlib-compression-error/#comments http://software.intel.com/en-us/articles/ipp-zlib-compression-error/ Intel® C++ Compiler for Linux* Knowledge Base Intel® C++ Compiler for Mac OS X* Knowledge Base Intel® C++ Compiler for Windows* Knowledge Base Intel® Integrated Performance Primitives Knowledge Base Intel® Parallel Composer Knowledge Base