Does it actually make sense? I remember somebody was strongly opposing
the idea of spawning threads in pixman in the past, but can't find
this e-mail right now.
Even if using multithreaded rendering is acceptable, the next question is
whether to rely on OpenMP for it. Currently OpenMP is disabled
On Mon, Jun 25, 2012 at 2:00 AM, Siarhei Siamashka
siarhei.siamas...@gmail.com wrote:
Some benchmarks with cairo-perf-trace (gcc 4.7.1, CFLAGS=-O2 -fopenmp):
=== Core i7 860 @2.8GHz ===
before patch:
[ 0] image firefox-fishtank 66.912 66.931 0.13% 3/3
export
Scale factor is selected to be nearly 1x, so that the MPix/s results
can be directly compared with the results of non-scaled compositing
operations.
---
test/lowlevel-blt-bench.c | 63 -
1 files changed, 62 insertions(+), 1 deletions(-)
diff --git
Using _mm_loadl_epi64() to load two pixels at once (pairs of top
and bottom pixels) is faster than loading each pixel separately
and combining them with _mm_set_epi32().
=== cairo-perf-trace ===
before: image firefox-fishtank 66.912 66.931 0.13%3/3
after: image
On Mon, Jun 18, 2012 at 9:09 PM, Søren Sandmann sandm...@cs.au.dk wrote:
Siarhei Siamashka siarhei.siamas...@gmail.com writes:
This is also a very useful test, but it effectively requires to have
an alternative double precision implementation for all the pixman
functionality to be verified.
