| 4 | | ||Description||Branch|| |
| 5 | | ||ARM optimized qdrawhelper is only enabled for RCVT (symbian) . The needs to be transferred to gcc inline assembly. This will optimize memfill, Source, SourceOver and some blend functions.|| || || || |
| 6 | | ||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.|| || || || |
| 7 | | ||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|| || || || |
| 9 | | ||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]|| || || |
| 10 | | ||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]|| |
| 11 | | ||Make QGifHandler::imageCount scan through the images. This can give a 5% speedup in the image_cycling reduction.|| || || || |
| 12 | | ||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|| || || || |
| 14 | | ||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|| || || || |
| 16 | | ||Changes to QHttpNetworkReply to reduce memory reallocations. Reserve some bytes instead of doing ''QByteArray::append'' all them time.|| || || || |
| 17 | | ||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] || |
| 18 | | ||Cut down on the usage of QUrl::toEncoded as it shows up in the profile of starting jobs.|| || || || |
| 19 | | ||QBENCHMARK results are hard to analyze and compare. We need a single and simple way to say if something is faster or slower. Be a bit like sunpsider, do the same math as well, mention slowest and fastest run.|| || || || |
| | 4 | ||Description||Branch||Created on||Landed in||Landed Date|| |
| | 5 | ||ARM optimized qdrawhelper is only enabled for RCVT (symbian) . The needs to be transferred to gcc inline assembly. This will optimize memfill, Source, SourceOver and some blend functions.|| || || || || |
| | 6 | ||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.|| || || || || |
| | 7 | ||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|| || || || || |
| | 9 | ||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]|| || || || |
| | 10 | ||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]|| 19.10.2009|| || || |
| | 11 | ||Make QGifHandler::imageCount scan through the images. This can give a 5% speedup in the image_cycling reduction.|| || || || || |
| | 12 | ||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|| || || || || |
| | 14 | ||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|| || || || || |
| | 16 | ||Changes to QHttpNetworkReply to reduce memory reallocations. Reserve some bytes instead of doing ''QByteArray::append'' all them time.|| || || || || |
| | 17 | ||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] || 19.10.2009|| || || |
| | 18 | ||Cut down on the usage of QUrl::toEncoded as it shows up in the profile of starting jobs.|| || || || || |
| | 19 | ||QBENCHMARK results are hard to analyze and compare. We need a single and simple way to say if something is faster or slower. Be a bit like sunpsider, do the same math as well, mention slowest and fastest run.|| || || || || |
