zlib-ng/zlib-ng

CI	Stable	Develop
GitHub Actions
CodeFactor
OSS-Fuzz
Codecov

zlib data compression library for the next generation systems

Maintained by Hans Kristian Rosbach aka Dead2 (zlib-ng àt circlestorm dót org)

• Zlib compatible API with support for dual-linking
• Modernized native API based on zlib API for ease of porting
• Modern C11 syntax and a clean code layout
• Deflate medium and quick algorithms based on Intel’s zlib fork
• Support for CPU intrinsics when available
  • Adler32 implementation using SSSE3, AVX2, AVX512, AVX512-VNNI, Neon, VMX & VSX
  • CRC32-B implementation using PCLMULQDQ, VPCLMULQDQ, ACLE, & IBM Z
  • Slide hash implementations using SSE2, AVX2, ARMv6, Neon, VMX & VSX
  • Compare256 implementations using SSE2, AVX2, Neon, POWER9 & RVV
  • Inflate chunk copying using SSE2, SSSE3, AVX, Neon & VSX
  • Support for hardware-accelerated deflate using IBM Z DFLTCC
• Unaligned memory read/writes and large bit buffer improvements
• Includes improvements from Cloudflare and Intel forks
• Configure, CMake, and NMake build system support
• Comprehensive set of CMake unit tests
• Code sanitizers, fuzzing, and coverage
• GitHub Actions continuous integration on Windows, macOS, and Linux
  • Emulated CI for ARM, AARCH64, PPC, PPC64, RISCV, SPARC64, S390x using qemu

The motivation for this fork was seeing several 3rd party contributions with new optimizations not getting implemented into the official zlib repository.

Mark Adler has been maintaining zlib for a very long time, and he has done a great job and hopefully he will continue for a long time yet. The idea of zlib-ng is not to replace zlib, but to co-exist as a drop-in replacement with a lower threshold for code change.

zlib has a long history and is incredibly portable, even supporting many systems that predate the Internet.
That is great, but it can complicate further development and maintainability. The zlib code contains many workarounds for really old compilers or to accommodate systems with limitations such as operating in a 16-bit environment.

Many of these workarounds are only maintenance burdens, some of them are pretty huge code-wise. With many workarounds cluttered throughout the code, it makes it harder for new programmers with an idea/interest for zlib to contribute.

I decided to make a fork, merge all the Intel optimizations, some of the Cloudflare optimizations, plus a couple other smaller patches. Then started cleaning out workarounds, various dead code, all contrib and example code.
The result is a better performing and easier to maintain zlib-ng.

A lot of improvements have gone into zlib-ng since its start, and numerous people and companies have contributed both small and big improvements, or valuable testing.

^{Please read LICENSE.md, it is very simple and very liberal.}

There are two ways to build zlib-ng:

To build zlib-ng using the cross-platform makefile generator cmake.

cmake .
cmake --build . --config Release
ctest --verbose -C Release

Alternatively, you can use the cmake configuration GUI tool ccmake:

ccmake .

To build zlib-ng using the bash configure script:

./configure
make
make test

WARNING: We do not recommend manually installing unless you really know what you are doing, because this can potentially override the system default zlib library, and any incompatibility or wrong configuration of zlib-ng can make the whole system unusable, requiring recovery or reinstall. If you still want a manual install, we recommend using the /opt/ path prefix.

For Linux distros, an alternative way to use zlib-ng (if compiled in zlib-compat mode) instead of zlib, is through the use of the LD_PRELOAD environment variable. If the program is dynamically linked with zlib, then the program will temporarily attempt to use zlib-ng instead, without risking system-wide instability.

LD_PRELOAD=/opt/zlib-ng/libz.so.1.2.13.zlib-ng /usr/bin/program

To install zlib-ng system-wide using cmake:

cmake --build . --target install

To install zlib-ng system-wide using the configure script:

make install

After building with cmake, an installation package can be created using cpack. By default a tgz package is created, but you can append -G <format> to each command to generate alternative packages types (TGZ, ZIP, RPM, DEB). To easily create a rpm or deb package, you would use -G RPM or -G DEB respectively.

cd build
cpack --config CPackConfig.cmake
cpack --config CPackSourceConfig.cmake

Alternatively, you can build and install zlib-ng using the vcpkg dependency manager:

git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh # "./bootstrap-vcpkg.bat" for powershell
./vcpkg integrate install
./vcpkg install zlib-ng

The zlib-ng port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.

Zlib-ng is aiming to be open to contributions, and we would be delighted to receive pull requests on github. Help with testing and reviewing pull requests etc is also very much appreciated.

Please check the Wiki for more info: Contributing

Thanks go out to all the people and companies who have taken the time to contribute code reviews, testing and/or patches. Zlib-ng would not have been nearly as good without you.

The deflate format used by zlib was defined by Phil Katz.
The deflate and zlib specifications were written by L. Peter Deutsch.

zlib was originally created by Jean-loup Gailly (compression) and Mark Adler (decompression).

• Fork of the popular minizip https://github.com/zlib-ng/minizip-ng
• Python tool to benchmark minigzip/minideflate https://github.com/zlib-ng/deflatebench
• Python tool to benchmark pigz https://github.com/zlib-ng/pigzbench
• 3rd party patches for zlib-ng compatibility https://github.com/zlib-ng/patches