ChangeLog: Acknowledge 2.0.6 release

This commit is contained in:
DRC
2020-10-14 14:46:30 -05:00
parent ae08115d4d
commit 460dfe40e1

View File

@@ -1,7 +1,7 @@
2.1 pre-beta 2.1 pre-beta
============ ============
### Significant changes relative to 2.0.5: ### Significant changes relative to 2.0.6:
1. The build system, x86-64 SIMD extensions, and accelerated Huffman codec now 1. The build system, x86-64 SIMD extensions, and accelerated Huffman codec now
support the x32 ABI on Linux, which allows for using x86-64 instructions with support the x32 ABI on Linux, which allows for using x86-64 instructions with
@@ -80,11 +80,17 @@ limit the number of allowable scans in the input file.
- Both programs now accept a `-strict` argument, which can be used to - Both programs now accept a `-strict` argument, which can be used to
treat all warnings as fatal. treat all warnings as fatal.
10. Fixed "using JNI after critical get" errors that occurred on Android
2.0.6
=====
### Significant changes relative to 2.0.5:
1. Fixed "using JNI after critical get" errors that occurred on Android
platforms when using any of the YUV encoding/compression/decompression/decoding platforms when using any of the YUV encoding/compression/decompression/decoding
methods in the TurboJPEG Java API. methods in the TurboJPEG Java API.
11. Fixed or worked around multiple issues with `jpeg_skip_scanlines()`: 2. Fixed or worked around multiple issues with `jpeg_skip_scanlines()`:
- Fixed segfaults or "Corrupt JPEG data: premature end of data segment" - Fixed segfaults or "Corrupt JPEG data: premature end of data segment"
errors in `jpeg_skip_scanlines()` that occurred when decompressing 4:2:2 or errors in `jpeg_skip_scanlines()` that occurred when decompressing 4:2:2 or
@@ -97,7 +103,7 @@ with `jpeg_skip_scanlines()`, and the issues could not readily be fixed.
- Fixed an issue whereby `jpeg_skip_scanlines()` always returned 0 when - Fixed an issue whereby `jpeg_skip_scanlines()` always returned 0 when
skipping past the end of an image. skipping past the end of an image.
12. The ARM 64-bit (ARMv8) NEON SIMD extensions can now be built using MinGW 3. The ARM 64-bit (ARMv8) NEON SIMD extensions can now be built using MinGW
toolchains targetting ARM64 (AArch64) Windows binaries. toolchains targetting ARM64 (AArch64) Windows binaries.
4. Fixed unexpected visual artifacts that occurred when using 4. Fixed unexpected visual artifacts that occurred when using