[Pixman] [PATCH 2/2] ARM: Add 'neon_composite_over_n_8888_0565' fast path

Taekyun Kim podain77 at gmail.com
Wed Apr 6 23:37:21 PDT 2011

2011/4/7 Siarhei Siamashka siarhei.siamashka at gmail.com

> I could not come up with any better solution other than just using
> different indentation for logically independent code blocks. Something
> like converting:

Yeah, I've seen that in your recent neon patches for bilinear.
I think it is a reasonable way to distinguish between logical code blocks.

> I think it might be interesting for you. I also have the following
> experimental branch:
> http://cgit.freedesktop.org/~siamashka/pixman/log/?h=playground/slow-path-reporter
> It collects statistics about what operations do not have optimized
> fast paths, along with the number of uses of these operations, total
> number of pixels processed, average number of pixels per operation and
> average scanline length. The code is currently linux specific and
> writes results to syslog. These results can be converted into a more
> human readable form by a script. I'm using it quite successfully and
> it revealed some of the missing optimizations which would be hard to
> identify in some other way.

This is actually a great help for me!!
Thanks :-)

Best Regards,
Taekyun Kim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pixman/attachments/20110407/fa120a13/attachment.htm>

More information about the Pixman mailing list