[cairo] Pixman merging - please don't touch pixman

Behdad Esfahbod behdad at behdad.org
Tue Apr 17 11:44:51 PDT 2007

On Tue, 2007-04-17 at 13:07 -0400, Soeren Sandmann wrote:
> Hi,
> As a heads up, I am currently working on merging the pixman/fb
> implementations. Since I'll be merging pixman into fb, I ask that
> people
>          don't commit substantial stuff to pixman
> without first talking to me (I'm ssp on IRC). I don't intend to
> discourage pixman development; just talk to me first before merging.

This is great news Soeren!

Just want to note the recent changes that went into pixman.  Mathias
Hasselmann and Chris Wilson committed series of patches that remove
mallocs from pixman in favor of stack and struct-embedded objects.  The
most essential of this was to remove malloc for pixman regions.  That
reduced the number of mallocs for a benchmark run against the image
surface by 40%.

There is also another such patch in the works.  Other than that I don't
think there is any other substantial pixman patchset around.  Oh, there
is also the altivec patch.

> Here is a rough roadmap:
> 1. Get libraries back in sync. There are performance improvements in
>    pixman, and bugfixes and new features in X. For various reasons
>    it's better to bring the X version up to pixman rather than the
>    other way around.
> 2. Make the switch-of-doom code in fbpict use fbCompositeRect() as
>    another special case. Ie., get rid of duplicated region walking
>    code.
> 3. Write new library. Add region code from pixman. 

Humm, a real separate shared library?

> 4. Starting with fbCompositeRect(), move code from X to the library
>    gradually, while keeping things working at all times.
> 5. Link cairo to the new library.
> Soren


"Those who would give up Essential Liberty to purchase a little
 Temporary Safety, deserve neither Liberty nor Safety."
        -- Benjamin Franklin, 1759

More information about the cairo mailing list