[poppler] Why does Gfx::opTab need to be built at runtime?

Kristian Høgsberg krh at bitplanet.net
Fri Sep 28 14:24:39 PDT 2007


On 9/26/07, Krzysztof Kowalczyk <kkowalczyk at gmail.com> wrote:
> On 9/26/07, Jeff Muizelaar <jeff at infidigm.net> wrote:
> > On Wed, Sep 26, 2007 at 11:03:17PM -0400, Jeff Muizelaar wrote:
> > > gcc does not produce any code for this afaict. I can't understand why
> > > visualc would be, unless you are just disassembling the .data section.
> >
> > It also looks like the table could be made const.
>
> Yes. I actually did that except it didn't show any improvements with
> msvc so I didn't commit the change. But on unix at the very least it
> should move this data to read-only of the dll, so less memory would be
> used if multiple processes used libpoppler. Not 100% sure if the
> presence of relocatable data (function pointers) doesn't prevent that.

If the functions are static, the function pointers in the table
shouldn't generate relocations.

Kristian


More information about the poppler mailing list