Searched refs:NEEDBITS (Results 1 - 3 of 3) sorted by relevance

/vbox/src/libs/zlib-1.2.6/contrib/infback9/
H A Dinfback9.c150 #define NEEDBITS(n) \ macro
284 NEEDBITS(3);
317 NEEDBITS(32);
348 NEEDBITS(14);
365 NEEDBITS(3);
392 NEEDBITS(here.bits);
398 NEEDBITS(here.bits + 2);
410 NEEDBITS(here.bits + 3);
417 NEEDBITS(here.bits + 7);
518 NEEDBITS(extr
[all...]
/vbox/src/libs/zlib-1.2.6/
H A Dinfback.c183 #define NEEDBITS(n) \ macro
299 NEEDBITS(3);
329 NEEDBITS(32);
360 NEEDBITS(14);
379 NEEDBITS(3);
411 NEEDBITS(here.bits + 2);
423 NEEDBITS(here.bits + 3);
430 NEEDBITS(here.bits + 7);
540 NEEDBITS(state->extra);
573 NEEDBITS(stat
[all...]
H A Dinflate.c498 #define NEEDBITS(n) \ macro
545 next state. The NEEDBITS() macro is usually the way the state evaluates
546 whether it can proceed or should return. NEEDBITS() does the return if
550 NEEDBITS(n);
554 where NEEDBITS(n) either returns from inflate() if there isn't enough
560 and a NEEDBITS(8), then BITS(8) would return the next byte in the stream.
562 NEEDBITS(n) uses PULLBYTE() to get an available byte of input, or to return
569 if NEEDBITS() returns in the loop. For example, want, need, and keep
570 would all have to actually be part of the saved state in case NEEDBITS()
575 NEEDBITS(
[all...]

Completed in 64 milliseconds