lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5741 Pars


From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5741 Parse inline scheme using per-expression port
Date: Sat, 22 Feb 2020 18:40:43 -0000

For the record, here with patch operative:
real 42m2.760s

that corresponds with "about 40 minutes" you talked about earlier?

No, that's more in line with the 50 minutes for the whole Patchy run. Here is the output from some older Patchy mail:

23:45:48 (UTC) Begin LilyPond compile, previous commit at
9f1683921621b612b94080d506ee317b058b29c8
23:45:56 Merged staging, now at: 9f1683921621b612b94080d506ee317b058b29c8
23:45:57 Success: ./autogen.sh --noconfigure
23:46:10 Success: /tmp/lilypond-autobuild/configure --enable-checking
23:46:13 Success: nice make clean
23:50:25 Success: nice make -j9 CPU_COUNT=9
23:54:11 Success: nice make test -j9 CPU_COUNT=9
00:28:11 Success: nice make doc -j9 CPU_COUNT=9
00:28:16 To ssh://git.sv.gnu.org/srv/git/lilypond.git
8b06b051f2..9f16839216 test-staging -> master
00:28:16 Success: pushed to master

As you can see, the doc build there takes 34 minutes, the whole run 43 minutes.


[issues:#5741] Parse inline scheme using per-_expression_ port

Status: Fixed
Labels: Fixed_2_21_0
Created: Fri Feb 07, 2020 02:52 PM UTC by Han-Wen Nienhuys
Last Updated: Sat Feb 22, 2020 05:52 PM UTC
Owner: Han-Wen Nienhuys

Introduces a throw-away string port, Overlay_string_port, which makes
a port out of a random section of a C string. It does not own the
string, so there is no overhead in creating and discarding the ports
during parse time.

For GUILE v2, Overlay_string_port uses UTF-8 encoding, so UTF-8
encoded string constants within the Scheme constants are interpreted
as Unicode correctly.

This obviates the string port that Source_file carries along.

This commit fixes a problem with GUILE 2.2.6, where LilyPond
calculates offsets in the source file as bytes, while GUILE interprets
the source file as UTF-8 encoded Unicode. As a result, files with
Unicode before embedded scheme break completely.

https://codereview.appspot.com/557330043


Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

_______________________________________________
Testlilyissues-auto mailing list
address@hidden
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

reply via email to

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