Searched refs:v6b (Results 1 – 25 of 27) sorted by relevance
12
20 derivative of libjpeg v6b developed by Miyasaka Masaru. The TigerVNC and61 API/ABI-compatible and mathematically compatible with libjpeg v6b. It can128 based on the libjpeg v6b code base. Although libjpeg v7 and v8 are not129 as widely used as v6b, enough programs (including a few Linux distros) made162 feature with libjpeg v6b (see rdswitch.c for an example.)244 the libjpeg v6b API/ABI as well. This allows the use of those functions by250 v6b or v7 API can pass an argument of `--without-mem-srcdst` to `configure` or257 the dynamic library version from 62.1.0 to 62.2.0 if using libjpeg v6b API/ABI279 v6b. The one exception to this is when using the floating point DCT/IDCT, in280 which case the outputs of libjpeg v6b and libjpeg-turbo can differ for the[all …]
131 libjpeg v6b (default), v7, or v8 emulation is enabled. If using Cygwin,186 *{version}* is 62, 7, or 8, depending on whether libjpeg v6b (default), v7, or229 depending on whether libjpeg v6b (default), v7, or v8 emulation is enabled.262 *{version}* is 62, 7, or 8, depending on whether libjpeg v6b (default), v7, or284 When using libjpeg v6b or v7 API/ABI emulation, add `-DWITH_MEM_SRCDST=0` to287 part of the original libjpeg v6b and v7 APIs, so removing them ensures strict296 v7 or v6b as well. The default is to enable both arithmetic encoding and866 libjpeg-turbo and libjpeg v6b. This also invokes the TurboJPEG unit tests,
152 option(WITH_ARITH_DEC "Include arithmetic decoding support when emulating the libjpeg v6b API/ABI" …154 option(WITH_ARITH_ENC "Include arithmetic encoding support when emulating the libjpeg v6b API/ABI" …158 …ibjpeg v7 API/ABI (this makes ${CMAKE_PROJECT_NAME} backward-incompatible with libjpeg v6b)" FALSE)160 …ibjpeg v8 API/ABI (this makes ${CMAKE_PROJECT_NAME} backward-incompatible with libjpeg v6b)" FALSE)162 … in-memory source/destination manager functions when emulating the libjpeg v6b or v7 API/ABI" TRUE)
290 Furthermore, there was never any good reason not to enable it with libjpeg v6b467 3-4x and decompression by about 2-2.5x (relative to libjpeg v6b) through the852 faster than libjpeg v6b.1008 libjpeg v6b or v7 emulation, so that programs can take advantage of these1013 libjpeg v6b or v7 API/ABI (or with previous versions of libjpeg-turbo.) See1229 and libjpeg-turbo should now produce identical output to libjpeg v6b in all1279 when the library is built with libjpeg v6b emulation.
146 respectively), preserving the legacy behavior of cjpeg v6b and prior. More (or407 Support for GIF input files was removed in cjpeg v6b due to concerns over
3010 As of v6b, the decompressor requires:
20 derivative of libjpeg v6b developed by Miyasaka Masaru. The TigerVNC and61 API/ABI-compatible and mathematically compatible with libjpeg v6b. It can128 based on the libjpeg v6b code base. Although libjpeg v7 and v8 are not129 as widely used as v6b, enough programs (including a few Linux distros) made161 feature with libjpeg v6b (see rdswitch.c for an example.)243 the libjpeg v6b API/ABI as well. This allows the use of those functions by249 v6b or v7 API can pass an argument of `-DWITH_MEM_SRCDST=0` to `cmake` prior to255 the dynamic library version from 62.2.0 to 62.3.0 if using libjpeg v6b API/ABI277 v6b. The one exception to this is when using the floating point DCT/IDCT, in278 which case the outputs of libjpeg v6b and libjpeg-turbo can differ for the[all …]
142 libjpeg v6b (default), v7, or v8 emulation is enabled. If using Cygwin,197 *{version}* is 62, 7, or 8, depending on whether libjpeg v6b (default), v7, or240 depending on whether libjpeg v6b (default), v7, or v8 emulation is enabled.273 *{version}* is 62, 7, or 8, depending on whether libjpeg v6b (default), v7, or295 When using libjpeg v6b or v7 API/ABI emulation, add `-DWITH_MEM_SRCDST=0` to298 part of the original libjpeg v6b and v7 APIs, so removing them ensures strict307 v7 or v6b as well. The default is to enable both arithmetic encoding and699 libjpeg-turbo and libjpeg v6b. This also invokes the TurboJPEG unit tests,
682 Furthermore, there was never any good reason not to enable it with libjpeg v6b859 3-4x and decompression by about 2-2.5x (relative to libjpeg v6b) through the1244 faster than libjpeg v6b.1401 libjpeg v6b or v7 emulation, so that programs can take advantage of these1406 libjpeg v6b or v7 API/ABI (or with previous versions of libjpeg-turbo.) See1622 and libjpeg-turbo should now produce identical output to libjpeg v6b in all1672 when the library is built with libjpeg v6b emulation.
144 respectively), preserving the legacy behavior of cjpeg v6b and prior. More (or
3028 As of v6b, the decompressor requires:
140 libjpeg v6b (default), v7, or v8 emulation is enabled. If using Cygwin,195 *{version}* is 62, 7, or 8, depending on whether libjpeg v6b (default), v7, or238 depending on whether libjpeg v6b (default), v7, or v8 emulation is enabled.271 *{version}* is 62, 7, or 8, depending on whether libjpeg v6b (default), v7, or293 When using libjpeg v6b or v7 API/ABI emulation, add `-DWITH_MEM_SRCDST=0` to296 part of the original libjpeg v6b and v7 APIs, so removing them ensures strict305 v7 or v6b as well. The default is to enable both arithmetic encoding and811 libjpeg-turbo and libjpeg v6b. This also invokes the TurboJPEG unit tests,
150 option(WITH_ARITH_DEC "Include arithmetic decoding support when emulating the libjpeg v6b API/ABI" …152 option(WITH_ARITH_ENC "Include arithmetic encoding support when emulating the libjpeg v6b API/ABI" …156 …ibjpeg v7 API/ABI (this makes ${CMAKE_PROJECT_NAME} backward-incompatible with libjpeg v6b)" FALSE)158 …ibjpeg v8 API/ABI (this makes ${CMAKE_PROJECT_NAME} backward-incompatible with libjpeg v6b)" FALSE)160 … in-memory source/destination manager functions when emulating the libjpeg v6b or v7 API/ABI" TRUE)
473 Furthermore, there was never any good reason not to enable it with libjpeg v6b650 3-4x and decompression by about 2-2.5x (relative to libjpeg v6b) through the1035 faster than libjpeg v6b.1192 libjpeg v6b or v7 emulation, so that programs can take advantage of these1197 libjpeg v6b or v7 API/ABI (or with previous versions of libjpeg-turbo.) See1413 and libjpeg-turbo should now produce identical output to libjpeg v6b in all1463 when the library is built with libjpeg v6b emulation.
5 libjpeg-turbo was originally based on libjpeg/SIMD, an MMX-accelerated derivative of libjpeg v6b de…
27 derivative of libjpeg v6b developed by Miyasaka Masaru. The TigerVNC and
70 derivative of libjpeg v6b developed by Miyasaka Masaru. The TigerVNC and
28 derivative of libjpeg v6b developed by Miyasaka Masaru. The TigerVNC and
75 Definition(v0_lo, v6b), Operand(v1_lo, v2b),119 Definition(v2_lo, v2b), Operand(v0_lo, v6b));
330 v6b = v6 | (1 << 7), enumerator397 static constexpr RegClass v6b{RegClass::v6b};