[cairo] Oprofiling Cairo on ARM

[Daniel Amelang]

On 11/28/06, Behdad Esfahbod <behdad at behdad.org> wrote:
> On Tue, 2006-11-28 at 15:43 -0500, Behdad Esfahbod wrote:
> > On Tue, 2006-11-28 at 14:46 -0500, Xan Lopez wrote:
> > > Anyway, the top
> > > offenders right now are: X, pangocairo and pango , with a special
> > > mention for a surprising g_type_check_is_a () (maybe someone should
> > > embark on a holy mission to remove every type checking which is
> > > outside of a public entry point in the API, if there's any around).
> >
> > I did some of these in pangocairo.  If you can give more details (which
> > functions or types are generating lots of this) I can look into it.
> > Which version of Pango do you use btw?
>
> Ok, I went on and dropped all significant ones.  Most were pretty safe
> to drop, others not.  It's committed to HEAD and pango-1-14 now.  Patch
> attached.
>
> I'm not sure what you'll get now if you try to render a PangoLayout
> created from a non-Cairo fontmap using pango_cairo_show_layout().  I'll
> do further tests and fix those issues.

Note that we haven't yet determined _where_ those type checks are
coming from. It may be that pangcairo is just fine in this regard.

Numbers forthcoming...I'm still struggling to whip my new 770 into shape.

Dan