Re: FT Performance Regression?

[Jamie Dale]

> Direct   rendering   using  FT_RASTER_FLAG_DIRECT   crashed   (bug
introduced in version 2.10.0).
Okay, fair enough, I was looking for something
mentioning FT_RASTER_FLAG_CLIP or clip_box.

> Does using clip_box solve it?
Yes, using the clip_box logic from my earlier email. Once again, not
documented nor called out in a release note. I've not looked at the code
for 2.10.1, but if all you've done is fixed the crash when
omitting FT_RASTER_FLAG_CLIP so that it uses an unbounded clip_box without
clamping it later (like gray_compute_cbox used to) then you're still
sitting on a 10x performance regression.

-Jamie.

On Sun, 27 Oct 2019 at 22:31, Alexei Podtelezhnikov <address@hidden>
wrote:

>
>
> On Oct 27, 2019, at 18:07, Jamie Dale <address@hidden>
> wrote:
>
> >  This is fixed in 2.10.1.
> Good to know. Once again, not called out in the upgrade notes.
>
>
> Huh? See line 70.
> http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/docs/CHANGES
>
> > What is the performance issue?
>
> Seriously, FT_Outline_Render is 10x slower is FreeType 2.10 than 2.6 with
> equivalent input. It's probably not noticeable to you unless you're doing
> real-time applications, but that is a *fantastically* bad regression for
> anyone using FreeType for games.
>
>
> Does using clip_box solve it?
>