Samples and standard libraries

[abraidwood]

Intel provide a Windows sample which contains a drop in replacement for the IJG jpeg library.

The new IPP 5 beta samples contain zlib and gzip compatible samples.

I think it would be very helpful to the community if Intel just provided (as sample source & possibly binaries) drop in replacements for these sorts of standard tools (bzip2 would be handy too) for both Windows and Linux (and in the future MacOS X platforms)

I find the fact that the gzip example has a different set of command line options very strange - sure you could extend them, but to change them means extra work for people & means adoption would be less likely.

Alistair

[Ying_S_Intel]

Thanks for your feedback, we will take these into our consideration for possible improvement around IPP 50 gold release.

By the way,could you please share some more information what exactly command line options you referred here? You may also open an issue with Intel Premier Support to follow up this issue with us.

Regards,
Ying S
Intel Corp.

[abraidwood]

Comparing the gzip command line we have:

gzip 1.2.4 (18 Aug 93)
usage: gzip [-cdfhlLnNrtvV19] [-S suffix] [file ...]
-c --stdout write on standard output, keep original files unchanged
-d --decompress decompress
-f --force force overwrite of output file and compress links
-h --help give this help
-l --list list compressed file contents
-L --license display software license
-n --no-name do not save or restore the original name and time stamp
-N --name save or restore the original name and time stamp
-q --quiet suppress all warnings
-r --recursive operate recursively on directories
-S .suf --suffix .suf use suffix .suf on compressed files
-t --test test compressed file integrity
-v --verbose verbose mode
-V --version display version number
-1 --fast compress faster
-9 --best compress better
file... files to (de)compress. If none given, use standard input.


Whereas with Intel's ippcompress_gzip we have:

Usage: ./ippcompress_gzip [-1|-2|-3|-4] [-e|-d] -sf source_file -df destination_file {-b number} {-sh strategy_hint}

-e Does the encoding of source_file using method 1..4 and writes results to 'destination_file'
-d Does the decoding of source_file using method 1..4 and writes results to 'destination_file'

-sf Specifies the source file name
-df Specifies the custom destination file name

-1 Does the BWT->MTF->RLE->Huffman encoding/decoding scheme
-2 Does the BWT->MTF->GIT encoding/decoding scheme
-3 Does the LZSS encoding/decoding scheme
-4 Does the LZ77 encoding/decoding scheme

-b (optional) Sets the custom size of the encoding input block from 1...9 where 1 means 100Kb, 2 means 200Kb, ... 9 means 900Kb

-sh (optional) Sets the strategy hint for GIT (f - fixed order, l - left reorder, r - right reorder)

Note, that order of the arguments is predefined.


This means that Intel's version cannot be used as a drop in replacement & given the number of places gzip can be used, it would be a substantial effort to switch, thus making the sample "interesting, but not useful"

Alistair