-
2012.07.03 17:53 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Tom Lane
-
2012.07.03 18:08 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Frank Warmerdam
- 2012.07.03 18:29 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Tom Lane
-
2012.07.04 16:26 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Bob Friesenhahn
-
2012.07.04 17:27 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Tom Lane
- 2012.07.04 19:49 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Bob Friesenhahn
-
2012.07.04 17:27 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Tom Lane
- 2012.07.03 18:09 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Dinar Valeev
-
2012.07.03 18:08 "Re: [Tiff] tiff 4.0.2 raw_decode test failing on ppc64", by Frank Warmerdam
2012.07.06 16:17 "Re: [Tiff] Crash in raw_decode with libjpeg 8d (was Re: tiff 4.0.2 raw_decode test failing on ppc64)", by Bob Friesenhahn
What version of libjpeg are you testing with?
Not speaking for others, but I suspect that old-timers like me still use the old good libjpeg 6b :-)
Debian is well into the transition to follow IJG JPEG. It is indeed true that there are multiple players now, including antique JPEG 6b.
I followed the advice and tried the following patch:
Thanks for this.
Which fixes the crash with 8b and make valgrind happy.
The ./raw_decode test still passes fine with jpeg 6b, but generates the following errors with 8b (after commenting the early exit in case of failures)
IJG JPEG 7+ use a new upsampling algorithm which is supposed to reduce round-trip error due to the sampling. However, I have noticed that it produces larger error or different results for certain files written with 6b.
Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/