Lines Matching full:machines
60 run-time option, because most machines can store 8-bit pixels much more
93 1. Memory usage. We want the code to be able to run on PC-class machines
99 2. Near/far pointer distinction. To run efficiently on 80x86 machines, the
102 fortunately it does not impact code quality for less brain-damaged machines,
111 problem on machines where char is wider than 8 bits. The library represents
210 by indirecting through a function pointer; on most machines this is no more
587 as "((value) & 0xFF)" on signed-char machines and "((int) (value))" elsewhere.
606 machines.
607 machines
647 enough on all machines of interest, on some machines it is preferable to use
665 On machines where malloc() can't handle a request bigger than 64Kb, this data
670 On 80x86 machines, the bottom-level pointer types (JSAMPROW and JBLOCKROW)
674 compiling on 80x86 machines and to nothing elsewhere.
748 memory, and it manages large "virtual" data arrays on machines where the
777 * On MS-DOS machines, large objects are referenced by FAR pointers,
781 type size_t, which may be 64K or less on some machines.
784 memory manager provides stripwise access to these arrays. On machines
865 jpeg_get_large, jpeg_free_large interface to FAR malloc/free in MSDOS machines;
