mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2026-01-04 19:10:20 +01:00
bed2701e1c
Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏ |
||
|---|---|---|
| .. | ||
| cairo-script | ||
| cairo-trace | ||
| .gitignore | ||
| backtrace-symbols.c | ||
| cairo-api-update | ||
| cairo-view | ||
| cairo.modules | ||
| COPYING | ||
| font-view.c | ||
| Makefile.am | ||
| malloc-stats.c | ||
| README | ||
| waterfall | ||
| xr2cairo | ||
Cairo Utilities =============== There are a varieties of utilities we use with cairo. backtrace-symbols ----------------- This is a small shared library designed to be preloaded by the linker and its purpose is to make the backtrace_symbols() function of glibc produce more useful source reference information. Build by: make backtrace-symbols.so and use by: LD_PRELOAD=$PWD/backtrace-symbols.so app-to-run This code should be contributed back to glibc at some point. malloc-stats ------------ This is a small shared library designed to be preloaded by the linker and its purpose is to make the malloc_stats() function of glibc produce more useful information. Build by: make malloc-stats.so and use by: LD_PRELOAD=$PWD/malloc-stats.so app-to-run This works best when backtrace-symbols is in use. That is: LD_PRELOAD="$PWD/backtrace-symbols.so $PWD/malloc-stats.so" app-to-run cairo-trace ----------- This tool can be used to trace all the cairo function calls made by an applications. This is useful for either extracting a test case triggering a bug from an application, or simply to get a general idea of how an application is using cairo. cairo-api-update and xr2cairo ----------------------------- These two scripts were used to convert source code written for pre-1.0 cairo to newer API. See $(top_srcdir)/PORTING_GUIDE for more information. These files are obsolete now and may be removed in a future version. cairo-view and waterfall ------------------------ These are two pycairo scripts useful for testing the toy font backend.