| 1 |
On 04/23/2012 10:40 PM, Chí-Thanh Christopher Nguyễn wrote: |
| 2 |
> Matt Turner schrieb: |
| 3 |
>> It's not that they're not supported, just that libjpeg-turbo doesn't |
| 4 |
>> have optimized routines for them. It'll still run fine. (Check the |
| 5 |
>> keywords, you'll see that it's stabilized.) |
| 6 |
> |
| 7 |
> And on those platforms it will run equally fast or faster or slower? |
| 8 |
> |
| 9 |
> |
| 10 |
> Best regards, |
| 11 |
> Chí-Thanh Christopher Nguyễn |
| 12 |
> |
| 13 |
|
| 14 |
based on what i've seen on mailinglists wrt libjpeg-turbo upstream: |
| 15 |
|
| 16 |
mostly equally, but due to later non-assembly improvements in IJG's |
| 17 |
jpeg, in some cases, a bit slower at least in 1.2.0 release of libjpeg-turbo |
| 18 |
but nothing anyone should be worried over about, as those changes are |
| 19 |
reviewed and/or in process of being reviewed and backported on as needed |
| 20 |
basis |
| 21 |
|
| 22 |
|
| 23 |
(almost left this message unsent because i'm totally lazy to dig up the |
| 24 |
references for above, sorry) |
| 25 |
|
| 26 |
- Samuli |
Archives