On Sat, Mar 13, 2021 at 11:30 PM Dr. Arne Babenhauserheide <arne_...@web.de> wrote:
> Also Guix is helping to push Guile towards the requirements of Lilypond > again — see > https://wingolog.org/archives/2020/06/03/a-baseline-compiler-for-guile > > Can I forward your results to the Guile mailing list? Yes. > > The evaluation speed of GUILE 3.x is still pretty poor. Having fast, > > JIT'ed code seems interesting in theory, but the way it's implemented > > in Guile 3.x is a giant headache: the separate byte compilation is > > extremely slow, and it is hard to manage (where should the .go files > > be stored/installed, how/when are they generated etc.). It also > > doesn't match our use case, because a lot of the code that we have > > comes from .ly files, so it cannot be precompiled. > > The article linked above shows that setting -O1 as optimization of the > code could help (if you’re not already doing that). The article gives a pointer to the code, which is module/language/tree-il/compile-bytecode.scm. I ran for c in $(git log module/language/tree-il/compile-bytecode.scm|grep commit|awk '{print $2;}'); do git show $c ; done | grep -i doc to look for documentation, but couldn't find it. The module has one exported symbol, which is compile-bytecode. Could you give some practical tips on how we'd use this? -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen