WarpJPEG.datatype 45.12 - now with AltiVec speed boost

[futaura]

In MorphOS JPEG datatype is already Altivec accelerated so unfortunately there is very little to gain.

AltiVec acceleration isn't just a matter of flicking a compiler switch though - the AltiVec optimisations in WarpJPEG are certainly not the same as in the MorphOS jpeg.datatype. I've no idea how good the AltiVec code is in the MorphOS datatype - it may be better/faster than WarpJPEG, or vice versa (I don't have the hardware to benchmark them).

[futaura]

True. Just out of interest, did you optimize it yourself or is it based on turbo-jpeg? Or both?

The AltiVec code came from libjpeg-turbo which became available earlier this year (although not in a release version yet).  But, unlike libjpeg-turbo, WarpJPEG is still mainly jpeg-9a based, with a bit of old code from jpeg-6b, and the libjpeg-turbo AltiVec code bolted on, with added optimisations and features from myself.  Hopefully it won't get too complicated to maintain this mix of code bases in the future .

[futaura]

Probably a dumb question, but I noticed your user icon has IBrowse in it.  Is that by any chance hinting at anything?  Can't speak for everyone on the forum, but I know I'd pay good money for some updates to that browser for classic systems.  *hint hint*  

Nice to hear . My avatar isn't new - it has been like that for quite a few years .  IBrowse has not been forgotten about though - it is going to be tough, but I fully intend for IBrowse 2.5 to be released at some point, especially as I'd rather all my work in it doesn't go completely to waste. The OS4 native version will get AltiVec in the internal JPEG decoder, of course. The main stumbling block, apart from Stefan, is AmiSSL right now - many websites have shut off SSL v3 completely, so IBrowse desperately needs the updated AmiSSL which is also being worked on (albeit very slowly).