Lines Matching refs:turbo

4 libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2,
6 x86, x86-64, ARM, and PowerPC systems.  On such systems, libjpeg-turbo is
8 systems, libjpeg-turbo can still outperform libjpeg by a significant amount, by
10 performance of libjpeg-turbo rivals that of proprietary high-speed JPEG codecs.
12 libjpeg-turbo implements both the traditional libjpeg API as well as the less
13 powerful but more straightforward TurboJPEG API.  libjpeg-turbo also features
18 libjpeg-turbo was originally based on libjpeg/SIMD, an MMX-accelerated
21 early 2010, libjpeg-turbo spun off into an independent project, with the goal
29 libjpeg-turbo is covered by three compatible BSD-style open source licenses.
33 Building libjpeg-turbo
39 Using libjpeg-turbo
42 libjpeg-turbo includes two APIs that can be used to compress and decompress
50   transforms on an image.  The Java interface for libjpeg-turbo is written on
56   more powerful.  The libjpeg API implementation in libjpeg-turbo is both
67 libjpeg-turbo includes extensions that allow JPEG images to be compressed
84 (decompression) to one of these values will cause libjpeg-turbo to read the
99 X byte is undefined, and in order to ensure the best performance, libjpeg-turbo
111 [jcstest.c](jcstest.c), located in the libjpeg-turbo source tree, demonstrates
122 built to use libjpeg v7 or v8 did not work with libjpeg-turbo, since it is
126 in libjpeg-turbo.  It should be noted, however, that this feature was added
129 without recompiling.  libjpeg-turbo does not claim to support all of the
135 version of libjpeg-turbo that emulates the libjpeg v7 or v8 ABI, so that
136 programs that are built against libjpeg v7 or v8 can be run with libjpeg-turbo.
145   libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
179 <http://www.libjpeg-turbo.org/About/SmartScale> and draw his/her own conclusions,
181 demonstrated sufficient usefulness to justify inclusion in libjpeg-turbo.
234 By default, libjpeg-turbo 1.3 and later includes the `jpeg_mem_src()` and
236 Previously, it was necessary to build libjpeg-turbo from source with libjpeg v8
242 libjpeg-turbo binaries.
247 libjpeg-turbo.  This will restore the pre-1.3 behavior, in which
257 is built against libjpeg-turbo 1.3+ and uses `jpeg_mem_src()` or
259 of libjpeg-turbo or against libjpeg v7- until the program actually tries to
261 If a program is built against the libjpeg-turbo 1.3+ DLL and uses
262 `jpeg_mem_src()` or `jpeg_mem_dest()`, then it must use the libjpeg-turbo 1.3+
273 For the most part, libjpeg-turbo should produce identical output to libjpeg
275 which case the outputs of libjpeg v6b and libjpeg-turbo can differ for the
278 - The SSE/SSE2 floating point DCT implementation in libjpeg-turbo is ever so
283 - When not using the SIMD extensions, libjpeg-turbo uses the more accurate
294 - If the floating point algorithms in libjpeg-turbo are not implemented using
298 While libjpeg-turbo does emulate the libjpeg v8 API/ABI, under the hood it is
300 cases in which libjpeg-turbo cannot be expected to produce the same output as
305   libjpeg-turbo's SIMD extensions are based on the libjpeg v6b behavior.
324 The optimized Huffman decoder in libjpeg-turbo does not handle restart markers
338 quality of 98-100.  Thus, libjpeg-turbo must use the non-SIMD quantization