Lines Matching full:large
101 "large" ones (kept in far data space). This is an annoying restriction, but
254 large, unwieldy, and hard to understand. To improve the situation, the
301 buffer large enough to accommodate the desired data chunk sizes. In other
713 must be large enough to hold a worst-case compressed MCU; a couple thousand
725 modifiable state is quite large and couldn't be copied cheaply. Instead it
748 memory, and it manages large "virtual" data arrays on machines where the
774 2. "Large" objects. These may require tens to hundreds of K depending on
777 * On MS-DOS machines, large objects are referenced by FAR pointers,
779 * Pool allocation heuristics may differ for large and small objects.
780 Note that individual "large" objects cannot exceed the size allowed by
782 3. "Virtual" objects. These are large 2-D arrays of JSAMPLEs or JBLOCKs
783 (typically large enough for the entire image being processed). The
788 (Note: JSAMPARRAY and JBLOCKARRAY data structures are a combination of large
802 making the in-memory buffers for virtual arrays be as large as possible.
811 realize routine must allow for space occupied by non-virtual large objects.
819 2. All "large" objects (including JSAMPARRAYs and JBLOCKARRAYs) must also be
