We finally have a version of LilyPond that can work with byte compiled files on GUILE 3. I had high hopes for this, given the ebullient promises of JIT in the release announcement. The results are disappointing. GUILE 3.0 is 3% faster than GUILE 2.2; both are about 30% slower than GUILE 1.8
I wanted to look more into the cause of this, and tried to run statprof. This prints a ton of ;;; (what! #<stack 7f60fbf7fc20>) lines. Then, the results look like 97.2% #x221bfb4 27.6% #x2215134 27.4% #x221836c 15.6% #x2215138 15.6% #x220ae70 15.6% profile-signal-handler at statprof.scm:251:4 15.6% #x2212b88 6.7% #x2218430 6.7% #x220ae70 6.7% profile-signal-handler at statprof.scm:251:4 6.7% #x2212b88 Is there a way to get insight into what these hex addresses (?) mean? -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen