[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ReactOS: stack vs heap
From: |
Werner LEMBERG |
Subject: |
Re: ReactOS: stack vs heap |
Date: |
Fri, 01 Sep 2023 15:15:26 +0000 (UTC) |
>> Perhaps a hybrid approach is the right one: Use the current
>> infrastructure up to a certain size, being as fast as possible because
>> dynamic allocation overhead can avoided, and resort to dynamic
>> allocation otherwise.
>
> FreeType is not shy about allocating buffers to load a glyph. This
> is just one more I highly doubt that it matters even at small
> sizes. We always allocate FT_Bitmap even for rendering too. As a
> matter of fact FreeType loses to the dense renderers when rendering
> complex glyphs precisely because of multiple restarts to fit the
> small buffer.
Well, I thought of a solution similar to Behdad's approach in commits
6f16b10019d7 and 56ddafa01ce2...
However, I leave that to you, since you've worked much more
intensively on the rendering code than me.
Werner
- Re: ReactOS: stack vs heap, Werner LEMBERG, 2023/09/01
- Re: ReactOS: stack vs heap, Alexei Podtelezhnikov, 2023/09/01
- Re: ReactOS: stack vs heap,
Werner LEMBERG <=
- Re: ReactOS: stack vs heap, Ben Wagner, 2023/09/01
- Re: ReactOS: stack vs heap, Alexei Podtelezhnikov, 2023/09/01
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/04
- Re: ReactOS: stack vs heap, Werner LEMBERG, 2023/09/04
- Re: ReactOS: stack vs heap, Behdad Esfahbod, 2023/09/05
- Re: ReactOS: stack vs heap, Werner LEMBERG, 2023/09/05