Lines Matching refs:turbo

4 libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2,
7 compression on x86 and x86-64 systems.  On such systems, libjpeg-turbo is
9 systems, libjpeg-turbo can still outperform libjpeg by a significant amount, by
11 performance of libjpeg-turbo rivals that of proprietary high-speed JPEG codecs.
13 libjpeg-turbo implements both the traditional libjpeg API as well as the less
14 powerful but more straightforward TurboJPEG API.  libjpeg-turbo also features
19 libjpeg-turbo was originally based on libjpeg/SIMD, an MMX-accelerated
22 early 2010, libjpeg-turbo spun off into an independent project, with the goal
30 libjpeg-turbo is covered by three compatible BSD-style open source licenses.
34 Building libjpeg-turbo
40 Using libjpeg-turbo
43 libjpeg-turbo includes two APIs that can be used to compress and decompress
51   transforms on an image.  The Java interface for libjpeg-turbo is written on
53   users of libjpeg-turbo.  Refer to [tjexample.c](tjexample.c) and
55   <http://libjpeg-turbo.org/Documentation/Documentation> for API documentation.
60   more powerful.  The libjpeg API implementation in libjpeg-turbo is both
72 libjpeg-turbo includes extensions that allow JPEG images to be compressed
89 (decompression) to one of these values will cause libjpeg-turbo to read the
104 X byte is undefined, and in order to ensure the best performance, libjpeg-turbo
116 [jcstest.c](jcstest.c), located in the libjpeg-turbo source tree, demonstrates
127 built to use libjpeg v7 or v8 did not work with libjpeg-turbo, since it is
131 in libjpeg-turbo.  It should be noted, however, that this feature was added
134 without recompiling.  libjpeg-turbo does not claim to support all of the
140 version of libjpeg-turbo that emulates the libjpeg v7 or v8 ABI, so that
141 programs that are built against libjpeg v7 or v8 can be run with libjpeg-turbo.
150   libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
184 <http://www.libjpeg-turbo.org/About/SmartScale> and draw his/her own conclusions,
186 demonstrated sufficient usefulness to justify inclusion in libjpeg-turbo.
239 By default, libjpeg-turbo 1.3 and later includes the `jpeg_mem_src()` and
241 Previously, it was necessary to build libjpeg-turbo from source with libjpeg v8
247 libjpeg-turbo binaries.
252 libjpeg-turbo.  This will restore the pre-1.3 behavior, in which
262 is built against libjpeg-turbo 1.3+ and uses `jpeg_mem_src()` or
264 of libjpeg-turbo or against libjpeg v7- until the program actually tries to
266 If a program is built against the libjpeg-turbo 1.3+ DLL and uses
267 `jpeg_mem_src()` or `jpeg_mem_dest()`, then it must use the libjpeg-turbo 1.3+
278 For the most part, libjpeg-turbo should produce identical output to libjpeg
280 which case the outputs of libjpeg v6b and libjpeg-turbo can differ for the
283 - The SSE/SSE2 floating point DCT implementation in libjpeg-turbo is ever so
288 - When not using the SIMD extensions, libjpeg-turbo uses the more accurate
299 - If the floating point algorithms in libjpeg-turbo are not implemented using
303 While libjpeg-turbo does emulate the libjpeg v8 API/ABI, under the hood it is
305 cases in which libjpeg-turbo cannot be expected to produce the same output as
310   libjpeg-turbo's SIMD extensions are based on the libjpeg v6b behavior.
329 The optimized Huffman decoder in libjpeg-turbo does not handle restart markers
343 quality of 98-100.  Thus, libjpeg-turbo must use the non-SIMD quantization