summaryrefslogtreecommitdiff
path: root/misc/valgrind-kpse-suppression.sup
diff options
context:
space:
mode:
authorPhilipp Gesang <phg@phi-gamma.net>2015-07-22 22:45:46 +0200
committerPhilipp Gesang <phg@phi-gamma.net>2015-07-22 22:45:49 +0200
commit1f360a62ce1f1b6cd4601e349718e414f64d8f35 (patch)
tree887fb96d7c283c2e948c808a21173934b4a13a06 /misc/valgrind-kpse-suppression.sup
parentd7ee402cbd34d509413d6115b27628351ef5f59f (diff)
downloadluaotfload-1f360a62ce1f1b6cd4601e349718e414f64d8f35.tar.gz
[init,main,package] split initialization in early and late stage
This is a big move. Due to the restructuring of the initialization we can now separate the early tasks -- mostly dirty stuff like writing globals -- from the later stage where we actually inject the actual font loader. As a consequence, the basic configuration is now present before the font loader is injected. It’s not complete, though, in that the reconfiguration step must still be executed after the font loader is there, since some config variables require values to be set up by the loader. A decision is pending regarding how we address the situation; possible approaches are, in order of increasing complexity: * reconfigure twice, skip some of the steps the first time through * split reconfiguration into two stages * make configuration independent of fontloader values Design-wise, the last point would be the most desirable, naturally. Though the fontloader has been known to require extensive static preparation which might very well make that strategy impossible or unjustifiably demanding. We’ll see how it plays out …
Diffstat (limited to 'misc/valgrind-kpse-suppression.sup')
0 files changed, 0 insertions, 0 deletions