[Pixman] pixman segv with mingw32 static

2013-03-13 Thread Dave Lawrence
Dear Pixman List, I am trying to cross-compiling pixman (0.28.2) and cairo (1.12.14) on linux for windows with mingw32 (4.2.1). If I build pixman static then my application bombs immediately with a segv in pixman_implementation_create_sse2() If I build the DLL then it works. If I configure --dis

Re: [Pixman] Proposal for pixman's glyph rendering: alpha correction

2013-03-13 Thread Bill Spitzak
I believe this is viable. The same rules can be used for anti-aliasing shapes and lines, too. Instead of 1-fg, I would guess the background to be a gray shade, with a value of 1 until the foreground color goes above a brightness threshold and then it should switch to fg-K where K is the thresh

Re: [Pixman] Several MIPS fast paths.

2013-03-13 Thread Nemanja Lukic
I'll push that as separate commit. -Original Message- From: pixman-bounces+nemanja.lukic=rt-rk@lists.freedesktop.org [mailto:pixman-bounces+nemanja.lukic=rt-rk@lists.freedesktop.org] On Behalf Of "Søren" Sandmann Sent: Thursday, March 07, 2013 12:57 AM To: Nemanja Lukic Cc: pixman@

[Pixman] Proposal for pixman's glyph rendering: alpha correction

2013-03-13 Thread Antti Lankila
I have a suggestion for getting sRGB-like text rendering without having sRGB alpha blending primitive. It's based on adjusting the alpha values of the glyph masks based on text foreground color without knowledge of the background color. I generated a writeup of it here: https://bel.fi/alankila/

Re: [Pixman] [PATCH] MIPS: DSPr2: Fix for bug in in_n_8 routine.

2013-03-13 Thread Nemanja Lukic
I support increasing number of iterations for blitters-test. This is what I usually leave overnight (make check), and which takes a lot of time for MIPS already with default number of iterations. Nemanja Lukic -Original Message- From: Siarhei Siamashka [mailto:siarhei.siamas...@gmail.com

Re: [Pixman] [PATCH] MIPS: DSPr2: Fix bug in over_n_8888_8888_ca/over_n_8888_0565_ca routines

2013-03-13 Thread Nemanja Lukic
I'll add this explanation to the commit message. On your remark, about splitting this into two commits, I really like that approach, but since I didn't do it this time (I don't have this intermediate result, where only bug is fixed, without code refactoring), I'll leave that for future bug fixes