…on for output and window. In this instance if too many bytes are written it will not correctly write matches with distances close to the window size.

Add support for selcting Thread sanitizer.

* There is no need to convert between unsigned and signed vector types. All relevant intrinsics have versions for all unsigned vector types.

* Using vdupq_n_u64 duplicates the unsigned 64-bit integer to two consecutive aligned memory locations in stack so compiler can use wider load instructions.
  All different-sized general-purpose registers overlay on ARM/AArch64, so any vector cast is no-op in assembly.

* chunkcopy() can read or write more than the safe length if the length is not multiple of chunk size.

…nings.

- Fix inflate corruption on aarch64 zlib-ng#1008
- Fix MSVC warnings zlib-ng#1002 zlib-ng#1013
- Minor chunkset improvements zlib-ng#1000 zlib-ng#994 zlib-ng#1015
- Minor cleanup zlib-ng#997
- Add CI test for pigz on aarch64 zlib-ng#1004
- Cmake improvements zlib-ng#996

Without this patch, #include <zlib.h> with Z_SOLO defined
(e.g. while building perl 5.34.0) fails because of use of
undefined types.

…e coverage.

…ple.

Do not use relative includes, since they are valid only within the
source directory. Rely on the build system to pass the necessary
include flags instead.

Transition to Ubuntu 18.04 in `GitHub` actions workflows.

Fixes:
```
Ubuntu 16.04 Clang
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.

Ubuntu 16.04 GCC
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
```

reported for example at:
https://github.com/zlib-ng/zlib-ng/actions/runs/1326434358

Official `GitHub` notice related to the removal of the 16.04 virtual
environments:
https://github.blog/changelog/2021-04-29-github-actions-ubuntu-16-04-lts-virtual-environment-will-be-removed-on-september-20-2021/

…viously failed test case.

…ier.

* armv7 has partial support for unaligned reads, but compiler might use instructions that do not support unaligned accesses

…erage in example.

Co-authored-by: concatime <concatime@users.noreply@github.com>
Co-authored-by: Mika Lindqvist <postmaster@raasu.org>

From ITK PR: InsightSoftwareConsortium/ITK#2803
CI check: https://github.com/InsightSoftwareConsortium/ITK/runs/3864083025

commit 5434d42 adds bad whitespace:
README.md:223: new blank line at EOF.

commit 5434d42 is not allowed; missing newline at the end of file in .gitattributes.

…e 0 through 0xFF inclusive.

…rroneous result in inffast.c.

Reorganize statements inside crc32_stub() to match more closely the format
used for other function stubs in functable.c.

…set_8.

When not using window, `window + wsize` applies a zero offset to a null pointer, which is undefined behavior.

Fix data loss warning.

Fixes:
```
itkzlib-ng/inflate.c(1209,24): warning C4267: '=': conversion from 'size_t' to 'unsigned long', possible loss of data
itkzlib-ng/inflate.c(1210,26): warning C4267: '=': conversion from 'size_t' to 'unsigned long', possible loss of data
```

… enabled.

* Use the self-hosted builder instead of ubuntu-latest.
* Drop qemu-related settings from DFLTCC configurations.
* Install codecov only for the current user, since the self-hosted
  builder runs under a restricted non-root account.
* Use actions/checkout@v2 for configure checks, since for some reason
  actions/checkout@v1 cannot find git on the self-hosted builder.
* Update the testing section of the DFLTCC README.
* Add the infrastructure code for the self-hosted builder.

Remove workaround in switchlevels.c, so we do actual testing of this.
Use named defines instead of magic numbers where we can.

This fixes link failures when using CFLAGS=-m31 on IBM Z. All the
other tests are already linked this way.

The zlib manual does not specify a strict contract for
inflateGetDictionary(), it merely says that it "Returns the sliding
dictionary being maintained by inflate", which is an implementation
detail. IBM Z inflate's behavior differs from that of software, and
may change in the future to boot.

When DFLTCC was introduced, deflateBound() was adjusted, but
compressBound() was not, leading to compression failures when using
compressBound() + compress() with poorly compressible data.

 - Fix hangs on macOS zlib-ng#1031
 - Fix minideflate write buffers being overwritten zlib-ng#1060
 - Fix deflateBound and compressBound returning too small size estimates zlib-ng#1049 zlib-ng#1071
 - Fix incorrect function declaration warning zlib-ng#1080
 - Fix build problems when building outside of source dir zlib-ng#1049
 - Fix build problems on arm2-7 zlib-ng#1030
 - Fixed some compile warnings zlib-ng#1020 zlib-ng#1036 zlib-ng#1037 zlib-ng#1048
 - Improved posix memalign support zlib-ng#888
 - Improvements to testing zlib-ng#637 zlib-ng#1026 zlib-ng#1032 zlib-ng#1035 zlib-ng#1049 zlib-ng#1051 zlib-ng#1056 zlib-ng#1063 zlib-ng#1067 zlib-ng#1079
 - Improvements for integration into other projects zlib-ng#1022 zlib-ng#1042
 - Code style fixes zlib-ng#637 zlib-ng#1040 zlib-ng#1050 zlib-ng#1075

Technically, we weren't actually doing this the way C wants us to,
legally.  The zmemcpy's turn into NOPs for pretty much all > 0
optimization levels and this gets us defined behavior with the
sanitizer, putting the optimized load by arbitrary alignment into the
compiler's hands instead of ours.

Backport note: Replaced zmemcpy with direct memcpy, as that is what we
end up with in a later commit anyway.

* This avoids conditional branch when it's known at build time that TZCNT instructions are always supported

It would seem that on some platforms, namely those which are
!UNALIGNED64_OK, there was a likelihood of chunkmemset_safe_c copying all
the bytes before passing control flow to chunkcopy, a function which is
explicitly unsafe to be called with a zero length copy.

This fixes that bug for those platforms.

Sample input from https://www.openwall.com/lists/oss-security/2022/03/26/1.

Co-authored-by: Tavis Ormandy <taviso@users.noreply.github.com>

Co-authored-by: Eric Biggers <ebiggers@kernel.org>

…zconf.h via zlib.h.

…e shell when running configure

…for small lengths due to shift returning 0.

* Treat 0 byte input as 1 byte input when calculating compressBound and deflateBound

* Test both compressBound() and deflateBound() as those share same code fragment.

…f GZBUFSIZE.

…late will now delete the input file.

…ssing and remove extension from output file path when decompressing.

…t supplied.

…t argument.

See zlib-ng#1262.

Signed-off-by: Vladislav Shchapov <vladislav@shchapov.ru>

Signed-off-by: Vladislav Shchapov <vladislav@shchapov.ru>

When building statically (i.e. with BUILD_SHARED_LIBS=OFF),
ZLIB_FULL_VERSION is not set resulting in an empty version in zlib.pc
and the following build failure with transmission:

checking for ZLIB... configure: error: Package requirements (zlib >= 1.2.3) were not met:

Package dependency requirement 'zlib >= 1.2.3' could not be satisfied.
Package 'zlib' has version '', required version is '>= 1.2.3'

Fixes:
 - http://autobuild.buildroot.org/results/b3b882482f517726e5c780ba4c37818bd379df82

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

…that use CMake and link against the zlib project can easily determine whether or not to include "zlib-ng.h" or "zlib.h".

Negative windowBits arguments are eventually turned positive in
deflateInit2_ and inflateInit2_ (more precisely in inflateReset2).
Such values are used to indicate that raw deflate/inflate should
be performed.

If a user supplies INT32_MIN for windowBits, the code will perform
-INT32_MIN which does not fit into int32_t. In fact, this is
undefined behavior in C and should be avoided.

Clearly this is a user error, but given the careful validation of
input arguments a few lines later in deflateInit2_ I think this
might be of interest.

Proof of Concept:

- Compile zlib-ng with gcc -ftrapv or -fsanitize=undefined
- Compile and run this program:

```
 #include <limits.h>
 #include <stdio.h>
 #include <zlib-ng.h>

 int main(void) {
  zng_stream de_stream = { 0 }, in_stream = { 0 };
  int result;

  result = zng_deflateInit2(&de_stream, 0, Z_DEFLATED, INT32_MIN,
      MAX_MEM_LEVEL, Z_DEFAULT_STRATEGY);
  printf("zng_deflateInit2: %d\n", result);

  result = zng_inflateInit2(&in_stream, INT32_MIN);
  printf("zng_inflateInit2: %d\n", result);

  return 0;
 }
```

If gzip support has been disabled during compilation then also
consider gzip relevant states as invalid in deflateStateCheck.

Also the gzip state definitions can be removed.

This change leads to failure in test/example, and I am not sure
what the GZIP conditional is trying to achieve. All gzip related
functions are still defined in zlib.h

Alternative approach is to remove the GZIP define.

…s compatibility.

…ming it is aligned in certain instances.

Backport note: Removed a lot of the original commit due to merge conflicts

  tools/maketrees.c:101:29: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
static void gen_trees_header()

  tools/makecrct.c:65:27: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
static void make_crc_table()