summaryrefslogtreecommitdiff
path: root/branches
diff options
context:
space:
mode:
authordcommander <dcommander@3789f03b-4d11-0410-bbf8-ca57d06f2519>2011-02-18 02:41:03 +0000
committerdcommander <dcommander@3789f03b-4d11-0410-bbf8-ca57d06f2519>2011-02-18 02:41:03 +0000
commit5d0095611dcfb44e76ab0cd092bcbafc007754c8 (patch)
tree5923831f21e3051bcd6af33fd971b2c0d990a0ee /branches
parenteb7386fae2439fdbcf052039751ecb78c3987520 (diff)
git-svn-id: https://libjpeg-turbo.svn.sourceforge.net/svnroot/libjpeg-turbo@379 3789f03b-4d11-0410-bbf8-ca57d06f2519
Diffstat (limited to 'branches')
-rw-r--r--branches/1.1.x/ChangeLog.txt6
1 files changed, 5 insertions, 1 deletions
diff --git a/branches/1.1.x/ChangeLog.txt b/branches/1.1.x/ChangeLog.txt
index 14d251a..100eddd 100644
--- a/branches/1.1.x/ChangeLog.txt
+++ b/branches/1.1.x/ChangeLog.txt
@@ -3,13 +3,17 @@
[1] The algorithm used by the SIMD quantization function cannot produce correct
results when the JPEG quality is >= 98 and the fast integer forward DCT is
-used. Thus, the non-SIMD quantization function is now used for those cases.
+used. Thus, the non-SIMD quantization function is now used for those cases,
+and libjpeg-turbo should now produce identical output to libjpeg v6b in all
+cases.
[2] Despite the above, the fast integer forward DCT still degrades somewhat for
JPEG qualities greater than 95, so TurboJPEG/OSS will now automatically use the
slow integer forward DCT when generating JPEG images of quality 96 or greater.
This reduces compression performance by as much as 15% for these high-quality
images but is necessary to ensure that the images are perceptually lossless.
+It also ensures that the library can avoid the performance pitfall created by
+[1].
[3] Ported jpgtest.cxx to pure C to avoid the need for a C++ compiler.