1285f41395
Writing transparent pixels is faster than the alternative, and we can skip clearing the frame to transparent. We'll still clear if the image is incomplete. I ran ./out/Release/nanobench --images <images> --samples 100 --sourceType image --simpleCodec -v over the GIFs we have on our bots, and found an average ~13% speedup. Raw data is on sheet 2 of https://docs.google.com/spreadsheets/d/19V-t9BfbFw5eiwBTKA1qOBkZbchjlTC5EIz6HFy-6RI/ (the sheet is named WriteTransparentPixels). GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2436183002 Review-Url: https://codereview.chromium.org/2436183002 |
||
---|---|---|
.. | ||
angle2 | ||
cpu-features | ||
etc1 | ||
expat | ||
freetype/include/freetype-android | ||
freetype2 | ||
gif | ||
giflib | ||
harfbuzz | ||
icu | ||
jsoncpp | ||
ktx | ||
libjpeg-turbo | ||
libmicrohttpd | ||
libpng | ||
libsdl | ||
libwebp | ||
lua | ||
native_app_glue | ||
qcms | ||
sfntly | ||
yasm | ||
zlib | ||
BUILD.gn | ||
README | ||
third_party.gni |
The third_party directory contains a set of dependencies from outside sources that are needed to build various components and tools within Skia. Some of these dependencies reside within the Skia repo, while others are pulled from other repositories and placed in the third_party/externals directory during build. These external dependencies are defined in a DEPS file. Products in third_party are subject to their own respective license terms. The license for each project should be included in the source itself via a license header or file. If the source itself does not include a license header or file, create a README that refers to reliable documentation of the project's license terms on the web.