Changes between Version 16 and Version 17 of QtBackLog


Ignore:
Timestamp:
Oct 23, 2009, 11:41:29 PM (15 years ago)
Author:
zecke@selfish.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • QtBackLog

    v16 v17  
    66||ARMv6 should be auto detected. Currently arm/armv6 can be passed as -embedded options. The benefit of ARMv6 in src/corelib is the use of atomic load and exchange, instead of the old "swap" extension. `__ARCH_ARM_6__` should be used to detect it.|| || ||
    77||Enabled pld (preload) in qdrawhelper for ARMv5te and upwards|| || ||
     8||Optimize scrolling of Windowsurfaces. Either optimize memcpy/memmove or consider using a tile based window surface|| || ||
    89||QImageReader deserves some optimatations. E.g. decode to the QImage provided to the decoder, do not parse every gif when trying to determine the size.||[http://qt.gitorious.org/~zecke/qt/zeckes-qt/commits/merge/qimagehandler-changes image-changes]|| ||
    910||Cut down on usage of QImage::scanLine inside Qt. This was already done in the GIF and PNG decoder.||[http://qt.gitorious.org/~zecke/qt/zeckes-qt/commits/merge/qimagehandler-changes image-changes]|| ||
    1011||Make QGifHandler::imageCount scan through the images. This can give a 5% speedup in the image_cycling reduction.|| || ||
    1112||Make picking a QImageIOHandler in QImageReader faster. Currently even the TIFF plugin is asked to handle images.|| || ||
     13||Consider creating a tile based QImage to allocate image chunks from an image pool with fixed size images|| || ||
    1214||Bring zero-copy to QIODevice... big one. That is good for networking and image decoding.|| || ||
     15||Consider creating a SharedBuffer that works on tiles/segments|| || ||
    1316||Changes to QHttpNetworkReply to reduce memory reallocations. Reserve some bytes instead of doing ''QByteArray::append'' all them time.|| || ||
    1417||Changes to QNetworkReply to remove quadratic runtime in QNetworkReplyHandler and latency fixes||[http://qt.gitorious.org/~zecke/qt/zeckes-qt/commits/merge/network-changes network-changes] || ||
    … …  
    2427||[https://bugs.webkit.org/show_bug.cgi?id=30293 #30293]||Loading speed regressed due image changes?||||
    2528||[https://bugs.webkit.org/show_bug.cgi?id=30301 #30301]||Loading bug/API bug on loading amazon in QtEmbedded Linux. Loading does not complete.||||
     29||[https://bugs.webkit.org/show_bug.cgi?id=29279 #29279]||Decode images to RGB16 or smaller (instead of RGB32) to conserve memory||||
    2630||||Go through the Palm changes and consider adopting them. Currently candidates are: Use stack/class memory in CSSParser, use JDCT_Fast for Jpeg decoding (to be achieved with QImageReader to set quality to 49), changes to Cached* to throw away encoded data more early. Palm avoids floating point operation on premultiplied alpha in setRGBA.||||
    27 ||||Using QImageReader::setQuality(49) will use JDCT_IFAST and promises to give a 5% speedup on image_cycling.||||
     31||[https://bugs.webkit.org/show_bug.cgi?id=30740 #30740]||Using QImageReader::setQuality(49) will use JDCT_IFAST and promises to give a 5% speedup on image_cycling.||||
    2832||||~~Image decoder changes needs to be measured. Do they make anything faster/slower? Do they consume more or less memory?~~||[https://trac.webkit.org/changeset/49179 49179ff]||