-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add zlib-ng 2.2.3 #109
Add zlib-ng 2.2.3 #109
Conversation
@data-man: Can you update your PR with latest zlib-ng? |
Sure, I'll try today. |
Actual version of Zlib-ng is 2.2.3. 2.1.0 is quite old and normally 2.2.3 is done here. |
I'm working on this, some progress with
|
Updated to zlib-ng 2.2.3. -typedef uint32_t (*zng_in_func) (void *, const uint8_t * *);
-typedef int32_t (*zng_out_func) (void *, uint8_t *, uint32_t);
+typedef uint32_t (*in_func) (void *, const uint8_t * *);
+typedef int32_t (*out_func) (void *, uint8_t *, uint32_t);
Z_EXTERN Z_EXPORT
-int32_t zng_inflateBack(zng_stream *strm, zng_in_func in, void *in_desc, zng_out_func out, void *out_desc);
+int32_t zng_inflateBack(zng_stream *strm, in_func in, void *in_desc, out_func out, void *out_desc);
/* In -int32_t Z_EXPORT PREFIX(inflateBack)(PREFIX3(stream) *strm, zng_in_func in, void *in_desc, zng_out_func out, void *out_desc) {
+int32_t Z_EXPORT PREFIX(inflateBack)(PREFIX3(stream) *strm, in_func in, void *in_desc, out_func out, void *out_desc) { |
Aren't these names clashing with zlib?
It would be better to use levels 1,6,9, 1 is fastest, 6 is default and 9 is best. Levels 2 and 5 are probably the least used in general. |
Thanks for your contribution. I cherry-picked your commit to https://github.com/inikep/lzbench/commits/update/ and it will be released with lzbench 2.0 |
@Neustradamus yes, of course There were small compilation issues with some platforms but the fix was easy:
|
Thank you! |
We can keep original zlib_ng files but then we need to compile zlib and zlib_ng from separate files e.g.: |
I'm not sure what are you asking. Whether to put it in separate file, not in _lzbench/compressors.cpp? |
@tansy I'm asking if it makes sense not to change original files and modify lzbench instead of a codec. Is it work doing or we should ignore it? |
If by 'modifing lzbench' you mean modifying `_lzbench/compressors.cpp::lzbench_zlib_ng_compress()' then I think it's better then modifying a codec - in case of codec's update you do it ('modifying a bench') once instead of doing it ('modifying a codec') all over again. One thing I don't get it here - why are these codecs, xz, csc, and apparently now zlib_ng get special treatment and are in separate files. |
No description provided.