Skip to contentSkip to conversation

libjpeg-turbo: update 1.4.1 -> 1.4.2

PATCH New Andre McCurdy 1 participant 1 message Nov 16, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libjpeg-turbo: update 1.4.1 -> 1.4.2

https://github.com/libjpeg-turbo/libjpeg-turbo/blob/1.4.2/ChangeLog.txt

1.4.2
=====

[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.

---
 .../jpeg/{libjpeg-turbo_8d+1.4.1.bb => libjpeg-turbo_8d+1.4.2.bb}     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-oe/recipes-core/jpeg/{libjpeg-turbo_8d+1.4.1.bb => libjpeg-turbo_8d+1.4.2.bb} (90%)
meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.2.bb renamed from meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb +2 -2
similarity index 90%
rename from meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb
rename to meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.2.bb
index e79f800..0138a63 100644
@@ -12,8 +12,8 @@ DEPENDS = "nasm-native"
 BASEPV = "${@d.getVar('PV',True).split('+')[1]}"
 
 SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${BASEPV}.tar.gz"
-SRC_URI[md5sum] = "b1f6b84859a16b8ebdcda951fa07c3f2"
-SRC_URI[sha256sum] = "4bf5bad4ce85625bffbbd9912211e06790e00fb982b77724af7211034efafb08"
+SRC_URI[md5sum] = "86b0d5f7507c2e6c21c00219162c3c44"
+SRC_URI[sha256sum] = "521bb5d3043e7ac063ce3026d9a59cc2ab2e9636c655a2515af5f4706122233e"
 
 S = "${WORKDIR}/${BPN}-${BASEPV}"
 
Signature · 1 line
1.9.1