./graphics/libjpeg-turbo, Accelerated libjpeg with SIMD instructions

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 2.0.5, Package name: libjpeg-turbo-2.0.5, Maintainer: dsainty

libjpeg-turbo is a version of libjpeg which uses MMX, SSE, and SSE2 SIMD
instructions to accelerate baseline JPEG compression/decompression by about
2-4x on x86 and x86-64 platforms. It will use NEON instructions on ARM.


Required to build:
[devel/nasm] [pkgtools/cwrappers]

Master sites:

SHA1: 9d4c565d402b2f5661be78d76098073ec7e30f10
RMD160: 3e820481675a3744f9fe2dbac3b80ae768d4b4da
Filesize: 2112.288 KB

Version history: (Expand)


CVS history: (Expand)


   2020-06-30 08:03:04 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
libjpeg-turbo: updated to 2.0.5

2.0.5

Significant changes relative to 2.0.4:

Worked around issues in the MIPS DSPr2 SIMD extensions that caused failures in \ 
the libjpeg-turbo regression tests. Specifically, the \ 
jsimd_h2v1_downsample_dspr2() and jsimd_h2v2_downsample_dspr2() functions in the \ 
MIPS DSPr2 SIMD extensions are now disabled until/unless they can be fixed, and \ 
other functions that are incompatible with big endian MIPS CPUs are disabled \ 
when building libjpeg-turbo for such CPUs.

Fixed an oversight in the TJCompressor.compress(int) method in the TurboJPEG \ 
Java API that caused an error ("java.lang.IllegalStateException: No source \ 
image is associated with this instance") when attempting to use that method \ 
to compress a YUV image.

Fixed an issue (CVE-2020-13790) in the PPM reader that caused a buffer overrun \ 
in cjpeg, TJBench, or the tjLoadImage() function if one of the values in a \ 
binary PPM/PGM input file exceeded the maximum value defined in the file's \ 
header and that maximum value was less than 255. libjpeg-turbo 1.5.0 already \ 
included a similar fix for binary PPM/PGM files with maximum values greater than \ 
255.

The TurboJPEG API library's global error handler, which is used in functions \ 
such as tjBufSize() and tjLoadImage() that do not require a TurboJPEG instance \ 
handle, is now thread-safe on platforms that support thread-local storage.
   2020-04-12 08:17:06 by Adam Ciarcinski | Files touched by this commit (7) | Package updated
Log message:
libjpeg-turbo: updated to 2.0.4

2.0.4

Fixed a regression in the Windows packaging system (introduced by 2.0 beta1[2]) \ 
whereby, if both the 64-bit libjpeg-turbo SDK for GCC and the 64-bit \ 
libjpeg-turbo SDK for Visual C++ were installed on the same system, only one of \ 
them could be uninstalled.

Fixed a signed integer overflow and subsequent segfault that occurred when \ 
attempting to decompress images with more than 715827882 pixels using the 64-bit \ 
C version of TJBench.

Fixed out-of-bounds write in tjDecompressToYUV2() and tjDecompressToYUVPlanes() \ 
(sometimes manifesting as a double free) that occurred when attempting to \ 
decompress grayscale JPEG images that were compressed with a sampling factor \ 
other than 1 (for instance, with cjpeg -grayscale -sample 2x2).

Fixed a regression introduced by 2.0.2[5] that caused the TurboJPEG API to \ 
incorrectly identify some JPEG images with unusual sampling factors as 4:4:4 \ 
JPEG images. This was known to cause a buffer overflow when attempting to \ 
decompress some such images using tjDecompressToYUV2() or \ 
tjDecompressToYUVPlanes().

Fixed an issue, detected by ASan, whereby attempting to losslessly transform a \ 
specially-crafted malformed JPEG image containing an extremely-high-frequency \ 
coefficient block (junk image data that could never be generated by a legitimate \ 
JPEG compressor) could cause the Huffman encoder's local buffer to be overrun. \ 
(Refer to 1.4.0[9] and 1.4beta1[15].) Given that the buffer overrun was fully \ 
contained within the stack and did not cause a segfault or other user-visible \ 
errant behavior, and given that the lossless transformer (unlike the \ 
decompressor) is not generally exposed to arbitrary data exploits, this issue \ 
did not likely pose a security risk.

The ARM 64-bit (ARMv8) NEON SIMD assembly code now stores constants in a \ 
separate read-only data section rather than in the text section, to support \ 
execute-only memory layouts.

2.0.3

Fixed "using JNI after critical get" errors that occurred on Android \ 
platforms when passing invalid arguments to certain methods in the TurboJPEG \ 
Java API.

Fixed a regression in the SIMD feature detection code, introduced by the AVX2 \ 
SIMD extensions (2.0 beta1[1]), that was known to cause an illegal instruction \ 
exception, in rare cases, on CPUs that lack support for CPUID leaf 07H (or on \ 
which the maximum CPUID leaf has been limited by way of a BIOS setting.)

The 4:4:0 (h1v2) fancy (smooth) chroma upsampling algorithm in the decompressor \ 
now uses a similar bias pattern to that of the 4:2:2 (h2v1) fancy chroma \ 
upsampling algorithm, rounding up or down the upsampled result for alternate \ 
pixels rather than always rounding down. This ensures that, regardless of \ 
whether a 4:2:2 JPEG image is rotated or transposed prior to decompression (in \ 
the frequency domain) or after decompression (in the spatial domain), the final \ 
image will be similar.

Fixed an integer overflow and subsequent segfault that occurred when attempting \ 
to compress or decompress images with more than 1 billion pixels using the \ 
TurboJPEG API.

Fixed a regression introduced by 2.0 beta1[15] whereby attempting to generate a \ 
progressive JPEG image on an SSE2-capable CPU using a scan script containing one \ 
or more scans with lengths divisible by 16 would result in an error \ 
("Missing Huffman code table entry") and an invalid JPEG image.

Fixed an issue whereby tjDecodeYUV() and tjDecodeYUVPlanes() would throw an \ 
error ("Invalid progressive parameters") or a warning \ 
("Inconsistent progression sequence") if passed a TurboJPEG instance \ 
that was previously used to decompress a progressive JPEG image.

2.0.2

Fixed a regression introduced by 2.0.1[5] that prevented a runtime search path \ 
(rpath) from being embedded in the libjpeg-turbo shared libraries and \ 
executables for macOS and iOS. This caused a fatal error of the form "dyld: \ 
Library not loaded" when attempting to use one of the executables, unless \ 
DYLD_LIBRARY_PATH was explicitly set to the location of the libjpeg-turbo shared \ 
libraries.

Fixed an integer overflow and subsequent segfault (CVE-2018-20330) that occurred \ 
when attempting to load a BMP file with more than 1 billion pixels using the \ 
tjLoadImage() function.

Fixed a buffer overrun (CVE-2018-19664) that occurred when attempting to \ 
decompress a specially-crafted malformed JPEG image to a 256-color BMP using \ 
djpeg.

Fixed a floating point exception that occurred when attempting to decompress a \ 
specially-crafted malformed JPEG image with a specified image width or height of \ 
0 using the C version of TJBench.

The TurboJPEG API will now decompress 4:4:4 JPEG images with 2x1, 1x2, 3x1, or \ 
1x3 luminance and chrominance sampling factors. This is a non-standard way of \ 
specifying 1x subsampling (normally 4:4:4 JPEGs have 1x1 luminance and \ 
chrominance sampling factors), but the JPEG format and the libjpeg API both \ 
allow it.

Fixed a regression introduced by 2.0 beta1[7] that caused djpeg to generate \ 
incorrect PPM images when used with the -colors option.

Fixed an issue whereby a static build of libjpeg-turbo (a build in which \ 
ENABLE_SHARED is 0) could not be installed using the Visual Studio IDE.

Fixed a severe performance issue in the Loongson MMI SIMD extensions that \ 
occurred when compressing RGB images whose image rows were not 64-bit-aligned.

2.0.1

Fixed a regression introduced with the new CMake-based Un*x build system, \ 
whereby jconfig.h could cause compiler warnings of the form "HAVE_*_H" \ 
redefined if it was included by downstream Autotools-based projects that used \ 
AC_CHECK_HEADERS() to check for the existence of locale.h, stddef.h, or \ 
stdlib.h.

The jsimd_quantize_float_dspr2() and jsimd_convsamp_float_dspr2() functions in \ 
the MIPS DSPr2 SIMD extensions are now disabled at compile time if the soft \ 
float ABI is enabled. Those functions use instructions that are incompatible \ 
with the soft float ABI.

Fixed a regression in the SIMD feature detection code, introduced by the AVX2 \ 
SIMD extensions (2.0 beta1[1]), that caused libjpeg-turbo to crash on Windows 7 \ 
if Service Pack 1 was not installed.

Fixed out-of-bounds read in cjpeg that occurred when attempting to compress a \ 
specially-crafted malformed color-index (8-bit-per-sample) Targa file in which \ 
some of the samples (color indices) exceeded the bounds of the Targa file's \ 
color table.

Fixed an issue whereby installing a fully static build of libjpeg-turbo (a build \ 
in which CFLAGS contains -static and ENABLE_SHARED is 0) would fail with \ 
"No valid ELF RPATH or RUNPATH entry exists in the file."

2.0.0

The TurboJPEG API can now decompress CMYK JPEG images that have subsampled M and \ 
Y components (not to be confused with YCCK JPEG images, in which the C/M/Y \ 
components have been transformed into luma and chroma.) Previously, an error was \ 
generated ("Could not determine subsampling type for JPEG image") when \ 
such an image was passed to tjDecompressHeader3(), tjTransform(), \ 
tjDecompressToYUVPlanes(), tjDecompressToYUV2(), or the equivalent Java methods.

Fixed an issue (CVE-2018-11813) whereby a specially-crafted malformed input file \ 
(specifically, a file with a valid Targa header but incomplete pixel data) would \ 
cause cjpeg to generate a JPEG file that was potentially thousands of times \ 
larger than the input file. The Targa reader in cjpeg was not properly detecting \ 
that the end of the input file had been reached prematurely, so after all valid \ 
pixels had been read from the input, the reader injected dummy pixels with \ 
values of 255 into the JPEG compressor until the number of pixels specified in \ 
the Targa header had been compressed. The Targa reader in cjpeg now behaves like \ 
the PPM reader and aborts compression if the end of the input file is reached \ 
prematurely. Because this issue only affected cjpeg and not the underlying \ 
library, and because it did not involve any out-of-bounds reads or other \ 
exploitable behaviors, it was not believed to represent a security threat.

Fixed an issue whereby the tjLoadImage() and tjSaveImage() functions would \ 
produce a "Bogus message code" error message if the underlying bitmap \ 
and PPM readers/writers threw an error that was specific to the readers/writers \ 
(as opposed to a general libjpeg API error.)

Fixed an issue (CVE-2018-1152) whereby a specially-crafted malformed BMP file, \ 
one in which the header specified an image width of 1073741824 pixels, would \ 
trigger a floating point exception (division by zero) in the tjLoadImage() \ 
function when attempting to load the BMP file into a 4-component image buffer.

Fixed an issue whereby certain combinations of calls to jpeg_skip_scanlines() \ 
and jpeg_read_scanlines() could trigger an infinite loop when decompressing \ 
progressive JPEG images that use vertical chroma subsampling (for instance, \ 
4:2:0 or 4:4:0.)

Fixed a segfault in jpeg_skip_scanlines() that occurred when decompressing a \ 
4:2:2 or 4:2:0 JPEG image using the merged (non-fancy) upsampling algorithms \ 
(that is, when setting cinfo.do_fancy_upsampling to FALSE.)

The new CMake-based build system will now disable the MIPS DSPr2 SIMD extensions \ 
if it detects that the compiler does not support DSPr2 instructions.

Fixed out-of-bounds read in cjpeg (CVE-2018-14498) that occurred when attempting \ 
to compress a specially-crafted malformed color-index (8-bit-per-sample) BMP \ 
file in which some of the samples (color indices) exceeded the bounds of the BMP \ 
file's color table.

Fixed a signed integer overflow in the progressive Huffman decoder, detected by \ 
the Clang and GCC undefined behavior sanitizers, that could be triggered by \ 
attempting to decompress a specially-crafted malformed JPEG image. This issue \ 
did not pose a security threat, but removing the warning made it easier to \ 
detect actual security issues, should they arise in the future.
   2020-03-13 18:55:33 by Tobias Nygren | Files touched by this commit (1)
Log message:
libjpeg-turbo: skip portability check for release/makemacpkg.in
   2020-01-26 18:32:28 by Roland Illig | Files touched by this commit (981)
Log message:
all: migrate homepages from http to https

pkglint -r --network --only "migrate"

As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.
   2019-11-02 23:38:06 by Roland Illig | Files touched by this commit (114)
Log message:
graphics: align variable assignments

pkglint -Wall -F --only aligned --only indent -r

No manual corrections.
   2018-08-13 22:50:59 by Greg Troxel | Files touched by this commit (3) | Package updated
Log message:
libjpeg-turbo: update to 1.5.3

Upstream changes are basically many bugfixes and a few performance improvements.
   2016-06-14 14:07:58 by Thomas Klausner | Files touched by this commit (5) | Package updated
Log message:
Updated libjpeg-turbo to 1.5.0.

1.5.0
=====

### Significant changes relative to 1.5 beta1:

1. Fixed an issue whereby a malformed motion-JPEG frame could cause the "fast
path" of libjpeg-turbo's Huffman decoder to read from uninitialized memory.

2. Added libjpeg-turbo version and build information to the global string table
of the libjpeg and TurboJPEG API libraries.  This is a common practice in other
infrastructure libraries, such as OpenSSL and libpng, because it makes it easy
to examine an application binary and determine which version of the library the
application was linked against.

3. Fixed a couple of issues in the PPM reader that would cause buffer overruns
in cjpeg if one of the values in a binary PPM/PGM input file exceeded the
maximum value defined in the file's header.  libjpeg-turbo 1.4.2 already
included a similar fix for ASCII PPM/PGM files.  Note that these issues were
not security bugs, since they were confined to the cjpeg program and did not
affect any of the libjpeg-turbo libraries.

4. Fixed an issue whereby attempting to decompress a JPEG file with a corrupt
header using the `tjDecompressToYUV2()` function would cause the function to
abort without returning an error and, under certain circumstances, corrupt the
stack.  This only occurred if `tjDecompressToYUV2()` was called prior to
calling `tjDecompressHeader3()`, or if the return value from
`tjDecompressHeader3()` was ignored (both cases represent incorrect usage of
the TurboJPEG API.)

5. Fixed an issue in the ARM 32-bit SIMD-accelerated Huffman encoder that
prevented the code from assembling properly with clang.

6. The `jpeg_stdio_src()`, `jpeg_mem_src()`, `jpeg_stdio_dest()`, and
`jpeg_mem_dest()` functions in the libjpeg API will now throw an error if a
source/destination manager has already been assigned to the compress or
decompress object by a different function or by the calling program.  This
prevents these functions from attempting to reuse a source/destination manager
structure that was allocated elsewhere, because there is no way to ensure that
it would be big enough to accommodate the new source/destination manager.

1.4.90 (1.5 beta1)
==================

### Significant changes relative to 1.4.2:

1. Added full SIMD acceleration for PowerPC platforms using AltiVec VMX
(128-bit SIMD) instructions.  Although the performance of libjpeg-turbo on
PowerPC was already good, due to the increased number of registers available
to the compiler vs. x86, it was still possible to speed up compression by about
3-4x and decompression by about 2-2.5x (relative to libjpeg v6b) through the
use of AltiVec instructions.

2. Added two new libjpeg API functions (`jpeg_skip_scanlines()` and
`jpeg_crop_scanline()`) that can be used to partially decode a JPEG image.  See
[libjpeg.txt](libjpeg.txt) for more details.

3. The TJCompressor and TJDecompressor classes in the TurboJPEG Java API now
implement the Closeable interface, so those classes can be used with a
try-with-resources statement.

4. The TurboJPEG Java classes now throw unchecked idiomatic exceptions
(IllegalArgumentException, IllegalStateException) for unrecoverable errors
caused by incorrect API usage, and those classes throw a new checked exception
type (TJException) for errors that are passed through from the C library.

5. Source buffers for the TurboJPEG C API functions, as well as the
`jpeg_mem_src()` function in the libjpeg API, are now declared as const
pointers.  This facilitates passing read-only buffers to those functions and
ensures the caller that the source buffer will not be modified.  This should
not create any backward API or ABI incompatibilities with prior libjpeg-turbo
releases.

6. The MIPS DSPr2 SIMD code can now be compiled to support either FR=0 or FR=1
FPUs.

7. Fixed additional negative left shifts and other issues reported by the GCC
and Clang undefined behavior sanitizers.  Most of these issues affected only
32-bit code, and none of them was known to pose a security threat, but removing
the warnings makes it easier to detect actual security issues, should they
arise in the future.

8. Removed the unnecessary `.arch` directive from the ARM64 NEON SIMD code.
This directive was preventing the code from assembling using the clang
integrated assembler.

9. Fixed a regression caused by 1.4.1[6] that prevented 32-bit and 64-bit
libjpeg-turbo RPMs from being installed simultaneously on recent Red Hat/Fedora
distributions.  This was due to the addition of a macro in jconfig.h that
allows the Huffman codec to determine the word size at compile time.  Since
that macro differs between 32-bit and 64-bit builds, this caused a conflict
between the i386 and x86_64 RPMs (any differing files, other than executables,
are not allowed when 32-bit and 64-bit RPMs are installed simultaneously.)
Since the macro is used only internally, it has been moved into jconfigint.h.

10. The x86-64 SIMD code can now be disabled at run time by setting the
`JSIMD_FORCENONE` environment variable to `1` (the other SIMD implementations
already had this capability.)

11. Added a new command-line argument to TJBench (`-nowrite`) that prevents the
benchmark from outputting any images.  This removes any potential operating
system overhead that might be caused by lazy writes to disk and thus improves
the consistency of the performance measurements.

12. Added SIMD acceleration for Huffman encoding on SSE2-capable x86 and x86-64
platforms.  This speeds up the compression of full-color JPEGs by about 10-15%
on average (relative to libjpeg-turbo 1.4.x) when using modern Intel and AMD
CPUs.  Additionally, this works around an issue in the clang optimizer that
prevents it (as of this writing) from achieving the same performance as GCC
when compiling the C version of the Huffman encoder
(<https://llvm.org/bugs/show_bug.cgi?id=16035>).  For the purposes of
benchmarking or regression testing, SIMD-accelerated Huffman encoding can be
disabled by setting the `JSIMD_NOHUFFENC` environment variable to `1`.

13. Added ARM 64-bit (ARMv8) NEON SIMD implementations of the commonly-used
compression algorithms (including the slow integer forward DCT and h2v2 & h2v1
downsampling algorithms, which are not accelerated in the 32-bit NEON
implementation.)  This speeds up the compression of full-color JPEGs by about
75% on average on a Cavium ThunderX processor and by about 2-2.5x on average on
Cortex-A53 and Cortex-A57 cores.

14. Added SIMD acceleration for Huffman encoding on NEON-capable ARM 32-bit
and 64-bit platforms.

    For 32-bit code, this speeds up the compression of full-color JPEGs by
about 30% on average on a typical iOS device (iPhone 4S, Cortex-A9) and by
about 6-7% on average on a typical Android device (Nexus 5X, Cortex-A53 and
Cortex-A57), relative to libjpeg-turbo 1.4.x.  Note that the larger speedup
under iOS is due to the fact that iOS builds use LLVM, which does not optimize
the C Huffman encoder as well as GCC does.

    For 64-bit code, NEON-accelerated Huffman encoding speeds up the
compression of full-color JPEGs by about 40% on average on a typical iOS device
(iPhone 5S, Apple A7) and by about 7-8% on average on a typical Android device
(Nexus 5X, Cortex-A53 and Cortex-A57), in addition to the speedup described in
[13] above.

    For the purposes of benchmarking or regression testing, SIMD-accelerated
Huffman encoding can be disabled by setting the `JSIMD_NOHUFFENC` environment
variable to `1`.

15. pkg-config (.pc) scripts are now included for both the libjpeg and
TurboJPEG API libraries on Un*x systems.  Note that if a project's build system
relies on these scripts, then it will not be possible to build that project
with libjpeg or with a prior version of libjpeg-turbo.

16. Optimized the ARM 64-bit (ARMv8) NEON SIMD decompression routines to
improve performance on CPUs with in-order pipelines.  This speeds up the
decompression of full-color JPEGs by nearly 2x on average on a Cavium ThunderX
processor and by about 15% on average on a Cortex-A53 core.

17. Fixed an issue in the accelerated Huffman decoder that could have caused
the decoder to read past the end of the input buffer when a malformed,
specially-crafted JPEG image was being decompressed.  In prior versions of
libjpeg-turbo, the accelerated Huffman decoder was invoked (in most cases) only
if there were > 128 bytes of data in the input buffer.  However, it is possible
to construct a JPEG image in which a single Huffman block is over 430 bytes
long, so this version of libjpeg-turbo activates the accelerated Huffman
decoder only if there are > 512 bytes of data in the input buffer.

18. Fixed a memory leak in tjunittest encountered when running the program
with the `-yuv` option.

1.4.2
=====

### Significant changes relative to 1.4.1:

1. Fixed an issue whereby cjpeg would segfault if a Windows bitmap with a
negative width or height was used as an input image (Windows bitmaps can have
a negative height if they are stored in top-down order, but such files are
rare and not supported by libjpeg-turbo.)

2. Fixed an issue whereby, under certain circumstances, libjpeg-turbo would
incorrectly encode certain JPEG images when quality=100 and the fast integer
forward DCT were used.  This was known to cause `make test` to fail when the
library was built with `-march=haswell` on x86 systems.

3. Fixed an issue whereby libjpeg-turbo would crash when built with the latest
& greatest development version of the Clang/LLVM compiler.  This was caused by
an x86-64 ABI conformance issue in some of libjpeg-turbo's 64-bit SSE2 SIMD
routines.  Those routines were incorrectly using a 64-bit `mov` instruction to
transfer a 32-bit JDIMENSION argument, whereas the x86-64 ABI allows the upper
(unused) 32 bits of a 32-bit argument's register to be undefined.  The new
Clang/LLVM optimizer uses load combining to transfer multiple adjacent 32-bit
structure members into a single 64-bit register, and this exposed the ABI
conformance issue.

4. Fixed a bug in the MIPS DSPr2 4:2:0 "plain" (non-fancy and non-merged)
upsampling routine that caused a buffer overflow (and subsequent segfault) when
decompressing a 4:2:0 JPEG image whose scaled output width was less than 16
pixels.  The "plain" upsampling routines are normally only used when
decompressing a non-YCbCr JPEG image, but they are also used when decompressing
a JPEG image whose scaled output height is 1.

5. Fixed various negative left shifts and other issues reported by the GCC and
Clang undefined behavior sanitizers.  None of these was known to pose a
security threat, but removing the warnings makes it easier to detect actual
security issues, should they arise in the future.
   2015-11-03 22:34:36 by Alistair G. Crooks | Files touched by this commit (610)
Log message:
Add SHA512 digests for distfiles for graphics category

Problems found with existing digests:
	Package fotoxx distfile fotoxx-14.03.1.tar.gz
	ac2033f87de2c23941261f7c50160cddf872c110 [recorded]
	118e98a8cc0414676b3c4d37b8df407c28a1407c [calculated]
	Package ploticus-examples distfile ploticus-2.00/plnode200.tar.gz
	34274a03d0c41fae5690633663e3d4114b9d7a6d [recorded]
	da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated]

Problems found locating distfiles:
	Package AfterShotPro: missing distfile AfterShotPro-1.1.0.30/AfterShotPro_i386.deb
	Package pgraf: missing distfile pgraf-20010131.tar.gz
	Package qvplay: missing distfile qvplay-0.95.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.