[Pixman] [PATCH 2/2] [mmx] Fix mask creation bugs

2010-04-07 Thread Søren Sandmann
From: Søren Sandmann Pedersen This line: mask = mask | mask >> 8 | mask >> 16 | mask >> 24; only works when mask has 0s in the lower 24 bits, so add mask &= 0xff00; before. Reported by Todd Rinaldo on the #cairo IRC channel. --- pixman/pixman-mmx.c |2 ++ 1 files changed, 2

[Pixman] [PATCH 1/2] Extend blitters test to first check known failure cases

2010-04-07 Thread Søren Sandmann
From: Søren Sandmann Pedersen This serves to make sure we don't accidentally reintroduce old bugs. --- test/blitters-test.c | 43 +++ 1 files changed, 43 insertions(+), 0 deletions(-) diff --git a/test/blitters-test.c b/test/blitters-test.c index 5e3303

Re: [Pixman] [cairo] Problem in pthread-specific thread-local storage macros in pixman?

2010-04-07 Thread Soeren Sandmann
Tor Lillqvist writes: > > A related question: Is there any support in the Windows versions of > > GCC for either __thread or __declspec(thread)? > > There is support for __thread (it gets recognized by the configure > script), but I strongly suspect it might be broken. > > I think I would prefe

Re: [Pixman] [cairo] [PATCHES] gradient color-tolerance/performance work

2010-04-07 Thread Chris Toshok
I've pushed changes to my git repo such that the double is passed all the way down, i.e.: void pixman_image_set_color_tolerance (pixman_image_t* image, double tolerance); The mapping is essentially unchanged, we just pick a different number of entries for the lookup tables depending on the v

Re: [Pixman] [cairo] pixman 0.18 MinGW SSE2 error

2010-04-07 Thread Soeren Sandmann
Hi, > Actually that SEGV Sven reported is familiar to me, too, since last > weekend. It is caused by the broken implementation of SSE2 intrinsics > in MinGW. For some reason variables of type __m128i (and __m128d, > presumably) don't get the 16-byte alignment they require. (I don't > know whether

Re: [Pixman] [cairo] Problem in pthread-specific thread-local storage macros in pixman?

2010-04-07 Thread Tor Lillqvist
> A related question: Is there any support in the Windows versions of > GCC for either __thread or __declspec(thread)? There is support for __thread (it gets recognized by the configure script), but I strongly suspect it might be broken. I think I would prefer to just use explicit code, as in the

Re: [Pixman] [cairo] pixman 0.18 MinGW SSE2 error

2010-04-07 Thread Tor Lillqvist
Actually that SEGV Sven reported is familiar to me, too, since last weekend. It is caused by the broken implementation of SSE2 intrinsics in MinGW. For some reason variables of type __m128i (and __m128d, presumably) don't get the 16-byte alignment they require. (I don't know whether the __m64* type