From: David Kastrup <dak@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 17147@debbugs.gnu.org
Subject: bug#17147: Performance regression by 3000000% for evaluating "and" form
Date: Tue, 01 Apr 2014 13:59:02 +0200 [thread overview]
Message-ID: <87ioqtjm61.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <877g79larq.fsf@fencepost.gnu.org> (David Kastrup's message of "Tue, 01 Apr 2014 10:22:17 +0200")
David Kastrup <dak@gnu.org> writes:
> If Guile is not going to optimize ..., I think it would be good if it
> led by example (its sources _are_ going to teach people how to program)
> and simply avoided using ... altogether, at the very least where
> recursive expansion rules are concerned.
>
> I have the suspicion, however, that there are a lot of tutorials/etc in
> the wild that do make use of ellipses. So while avoiding ... will help
> with keeping Guile's own internals scalable to large expressions, it
> will still likely affect the performance of a significant amount of
> third-party code.
By the way: module/system/vm/assembler.scm is taking an absolutely
insane amount of time to compile. It also makes copious use of syntax
rules including ... and this might be related.
--
David Kastrup
next prev parent reply other threads:[~2014-04-01 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 9:58 bug#17147: Performance regression by 3000000% for evaluating "and" form David Kastrup
2014-03-31 22:30 ` Mark H Weaver
2014-03-31 23:21 ` David Kastrup
2014-04-01 2:55 ` Mark H Weaver
2014-04-01 6:17 ` David Kastrup
2014-04-01 7:10 ` Mark H Weaver
2014-04-01 8:22 ` David Kastrup
2014-04-01 11:59 ` David Kastrup [this message]
2014-04-01 16:19 ` Mark H Weaver
2014-05-12 6:08 ` bug#17147: Another idea David Kastrup
2014-05-13 13:03 ` bug#17147: Scalability front and back David Kastrup
2014-06-04 14:18 ` bug#17147: [PATCH] Add versions of and/or avoiding O(n^2) argument matching David Kastrup
2014-06-05 1:09 ` Mark H Weaver
2014-06-05 4:06 ` David Kastrup
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=87ioqtjm61.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=17147@debbugs.gnu.org \
--cc=mhw@netris.org \
/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).