From: Maxime Devos <maximedevos@telenet.be>
To: Jean Abou Samra <jean@abou-samra.fr>,
guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Guile optimizations slowing down the program?
Date: Wed, 09 Mar 2022 08:28:06 +0100 [thread overview]
Message-ID: <5f680556a912ad3826f9f722d2e6b5bbcb7cc76f.camel@telenet.be> (raw)
In-Reply-To: <4f80c059-4e10-1c0b-33d4-e73c66da297c@abou-samra.fr>
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
Jean Abou Samra schreef op wo 09-03-2022 om 00:31 [+0100]:
> In summary, the less Guile optimizes, the faster LilyPond runs. Is that
> something expected?
I don't think so, but I don't have a clue how this happens ...
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-09 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 23:31 Guile optimizations slowing down the program? Jean Abou Samra
2022-03-09 7:28 ` Maxime Devos [this message]
2022-03-09 7:53 ` Dr. Arne Babenhauserheide
2022-03-09 10:01 ` Jean Abou Samra
2022-03-09 10:25 ` Dr. Arne Babenhauserheide
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f680556a912ad3826f9f722d2e6b5bbcb7cc76f.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=jean@abou-samra.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).