Searched refs:wrap (Results 1 – 7 of 7) sorted by relevance
113 if (state->wrap) /* to support ill-conceived Java test suite */ in inflateResetKeep()114 strm->adler = state->wrap & 1; in inflateResetKeep()142 int wrap; in inflateReset2() local153 wrap = 0; in inflateReset2()157 wrap = (windowBits >> 4) + 5; in inflateReset2()173 state->wrap = wrap; in inflateReset2()623 if (state->wrap == 0) { in inflate()629 if ((state->wrap & 2) && hold == 0x8b1f) { /* gzip header */ in inflate()640 if (!(state->wrap & 1) || /* check if zlib header allowed */ in inflate()686 if ((state->flags & 0x0200) && (state->wrap & 4)) in inflate()[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
41 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
2883 …- wrap indirectly included functions ([d95d56b](https://review.trustedfirmware.org/plugins/gitiles…4509 …- wrap toolchain paths in double quotes ([4731c00](https://review.trustedfirmware.org/plugins/giti…5995 …- wrap cache enabled assert under plat_can_cmo ([78fbb0e](https://review.trustedfirmware.org/plugi…7087 …- wrap cold_boot.h with MTK_SIP_KERNEL_BOOT_ENABLE ([24476b2](https://review.trustedfirmware.org/p…11953 retention states to be inside the locks and fixing handling of wrap-around