[Webkit-unassigned] [Bug 74286] [Chromium] Use decoding swizzle only on libjpeg-turbo 1.1.90+

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 13 02:08:03 PST 2011


Paweł Hajdan, Jr. <phajdan.jr at chromium.org> changed:

           What    |Removed                     |Added
                 CC|                            |phajdan.jr at chromium.org

--- Comment #4 from Paweł Hajdan, Jr. <phajdan.jr at chromium.org>  2011-12-13 02:08:03 PST ---
(In reply to comment #2)
> Is there any way to query the libjpeg-turbo version, either via macros,
> or in some sort of package configure script that can then set the appropriate Chrome build options?

Note that it's not just about compile-time compatibility. It should be possible to compile against libjpeg-turbo and then use vanilla libjpeg at run-time without problems.

Currently it's not the case, see https://bugs.gentoo.org/show_bug.cgi?id=393471#c3 and the next comment on that bug.

The fix for this should allow the users to use any of libjpeg, libjpeg-turbo at run time and get correct rendering.

> I kind of dislike turning this off for all "use system libraries" cases because then
> even systems with more recent libraries miss out on the optimization.

Arguably correctness is more important than performance. I don't find fast and broken rendering very useful.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list