lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guile 2 vs. Guile 3


From: Jean Abou Samra
Subject: Re: Guile 2 vs. Guile 3
Date: Mon, 28 Nov 2022 00:47:55 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0

Le 26/11/2022 à 22:36, Eric Benson a écrit :
In anticipation of the impending release of 2.24, I recently ported my
Lilypond files from 2.22 to 2.23.81. I have about 100 lead sheets with
lyrics, parameterized so that I can easily create them in different keys
and in treble clef or bass clef. There are all in the range of 1 to 2 pages
when typeset. I have a script that generates them in four different keys,
so that's roughly 400 invocations of lilypond.



The time to initialize LilyPond is roughly 0.1s, so 40s of the
5 minutes time are spent just initializing LilyPond 400 times.
Consider passing all the files to 'lilypond' in a single invocation,
which should be faster.


I know that Lilypond 2.24 binary distributions will be built with Guile 2,
not Guile 3, but I thought you might like to know that I was able to build
2.23.81 from source with Guile 3, run my script, and I got what appears to
be the exact same result as I had with the Guile 2 binary distribution.
This was on a Mac Studio with Apple CPU running MacOS Ventura 13.0.1. I'm
not sure if the Guile 3 JIT is enabled in this build, or if it even works
currently on Apple silicon.



A patch was recently posted on the Guile mailing list to add JIT
support on Apple Silicon [1] so I don't think it works currently.


https://lists.gnu.org/archive/html/guile-devel/2022-11/msg00021.html

Maybe you will see it failing if you set GUILE_JIT_THRESHOLD=0
in the environment?

Best,
Jean

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]