Searched refs:wrap (Results 1 – 7 of 7) sorted by relevance
128 if (state->wrap) /* to support ill-conceived Java test suite */129 strm->adler = state->wrap & 1;161 int wrap; local170 wrap = 0;174 wrap = (windowBits >> 4) + 5;190 state->wrap = wrap;658 if (state->wrap == 0) {664 if ((state->wrap & 2) && hold == 0x8b1f) { /* gzip header */676 if (!(state->wrap & 1) || /* check if zlib header allowed */721 if ((state->flags & 0x0200) && (state->wrap & 4))[all …]
86 int wrap; /* bit 0 true for zlib, bit 1 true for gzip, member
11 * and text will wrap when necessary.
31 result in a value large enough to wrap around, which may lead to unpredictable89 would wrap around. This may allow an attacker to copy unexpected data into
45 tasks, wrap CMake functions, etc. Since this functionality can be useful in
80 which wrap ``tf_log`` and which allow the logging call to be compiled-out
4520 retention states to be inside the locks and fixing handling of wrap-around
