Closed
Bug 489142
Opened 16 years ago
Closed 15 years ago
JPEG decoder does not use fastpath when CMS mode is tagged-only
Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
RESOLVED
FIXED
People
(Reporter: ilpo.ruotsalainen, Assigned: ilpo.ruotsalainen)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
789 bytes,
patch
|
joe
:
review+
benjamin
:
approval2.0+
|
Details | Diff | Splinter Review |
User-Agent: Opera/9.63 (X11; Linux i686; U; en) Presto/2.1.1
Build Identifier:
When CMS is enabled in tagged-only mode, the JPEG decoder does not use the direct YCC->ARGB path even for images where it could be used (ie. images without an ICC profile).
Reproducible: Always
| Assignee | ||
Comment 1•16 years ago
|
||
Average execution time for my JPEG loading benchmark case goes down from 414.67sec to 399.10sec on a 1GHz SnapDragon (ARMv7) with this patch.
Comment 2•16 years ago
|
||
Comment on attachment 373630 [details] [diff] [review]
Fix for the issue
Nice catch.
Do you need someone to check this in for you?
Attachment #373630 -
Flags: review+
Updated•16 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 3•16 years ago
|
||
(In reply to comment #2)
> Do you need someone to check this in for you?
Yes please.
Comment 4•15 years ago
|
||
Marking as checkin-needed.
Updated•15 years ago
|
Keywords: checkin-needed
Updated•15 years ago
|
Assignee: nobody → ilpo.ruotsalainen
Comment 5•15 years ago
|
||
And removing checkin-needed; I'll just check this in myself when my commit access request goes through.
Do we need to get another review of this, since the r+ is a year old? JOEDREW, what do you think?
Keywords: checkin-needed
Comment 6•15 years ago
|
||
If the patch still applies and/or only has some fuzz, check it in!
Updated•15 years ago
|
Attachment #373630 -
Flags: approval2.0?
Updated•15 years ago
|
Attachment #373630 -
Flags: approval2.0? → approval2.0+
Comment 7•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•