A MMX/SSE2 accelerated library for manipulating JPEG image files

Edit Package libjpeg-turbo

The libjpeg-turbo package contains a library of functions for manipulating
JPEG images.

Refresh
Refresh
Source Files
Filename Size Changed
baselibs.conf 0000000300 300 Bytes
libjpeg-1.4.0-ocloexec.patch 0000003014 2.94 KB
libjpeg-turbo-1.3.0-tiff-ojpeg.patch 0000001966 1.92 KB
libjpeg-turbo-1.5.1.tar.gz 0001650647 1.57 MB
libjpeg-turbo.changes 0000015299 14.9 KB
libjpeg-turbo.spec 0000004522 4.42 KB
libjpeg62-turbo.changes 0000015491 15.1 KB
libjpeg62-turbo.spec 0000003841 3.75 KB
Revision 33 (latest revision is 74)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 429280 from Ismail Dönmez's avatar Ismail Dönmez (namtrac) (revision 33)
- Update to version 1.5.1
  + Fix for PowerPC platforms lacking AltiVec instructions
  + Fix ABI problem with clang/llvm on aarch64.
  + Fancy upsampling is now supported when decompressing JPEG
    images that use 4:4:0 (h1v2) chroma subsampling.
  + If merged upsampling isn't SIMD-accelerated but YCbCr-to-RGB
    conversion is, then libjpeg-turbo will now disable merged
    upsampling when decompressing YCbCr JPEG images into RGB
    or extended RGB output images. This significantly speeds up
    the decompression of 4:2:0 and 4:2:2 JPEGs on ARM platforms
    if fancy upsampling is not used 
    (for example, if the -nosmooth option to djpeg is specified.)
  + The TurboJPEG API will now decompress 4:2:2 and 4:4:0 JPEG
    images with 2x2 luminance sampling factors and 2x1 or 1x2
    chrominance sampling factors.
  + Fixed an unsigned integer overflow in the libjpeg memory manager.
  + Fixed additional negative left shifts and other issues reported
    by the GCC and Clang undefined behavior sanitizers when
    attempting to decompress specially-crafted malformed JPEG
    images. None of these issues posed a security threat, but
    removing the warnings makes it easier to detect actual
    security issues, should they arise in the future.
  + Fixed an out-of-bounds array reference, introduced by
    1.4.902 and detected by the Clang undefined behavior sanitizer,
    that could be triggered by a specially-crafted malformed
    JPEG image with more than four components. Because the
    out-of-bounds reference was still within the same structure,
    it was not known to pose a security threat, but removing
    the warning makes it easier to detect actual security issues,
    should they arise in the future.
Comments 0
openSUSE Build Service is sponsored by