From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11657@debbugs.gnu.org
Subject: bug#11657: 24.1.50; Byte compiler is a lot slower now, when run interpreted
Date: Sun, 10 Jun 2012 21:10:07 -0400 [thread overview]
Message-ID: <jwvd356vfhv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <jwv62azw7l7.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 10 Jun 2012 10:48:39 -0400")
> Another would be to add some instrumentation code to the `pcase' macro,
> to output a message everytime the cache misses. E.g. use the patch below.
I tried that and found that the `pcase-let' macro was not memoized (it
goes through `pcase' but pcase's memoization fails in that case).
I added explicit memoization to pcase-let, which should
help significantly.
Please try it and tell me if it was the only source of slowdown.
BTW, regarding those problems, I'm experimenting with a change that
calls macroexpand-all directly from readevalloop, so as to avoid such
repeated macro-expansion.
Stefan
next prev parent reply other threads:[~2012-06-11 1:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 11:30 bug#11657: 24.1.50; Byte compiler is a lot slower now, when run interpreted Eli Zaretskii
2012-06-09 20:07 ` Juanma Barranquero
2012-06-09 23:36 ` Christoph Scholtes
2012-06-10 1:24 ` Stefan Monnier
2012-06-10 3:00 ` Eli Zaretskii
2012-06-10 14:48 ` Stefan Monnier
2012-06-11 1:10 ` Stefan Monnier [this message]
2012-06-11 16:53 ` Eli Zaretskii
2012-06-14 19:09 ` Stefan Monnier
2012-06-14 23:56 ` Juanma Barranquero
2012-06-15 1:41 ` Stefan Monnier
2012-06-15 9:27 ` Eli Zaretskii
2012-06-15 19:43 ` Juanma Barranquero
2012-06-15 20:04 ` Eli Zaretskii
2012-06-20 16:33 ` Stefan Monnier
2012-06-20 23:02 ` Juanma Barranquero
2012-06-22 18:33 ` Eli Zaretskii
2012-06-25 1:02 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvd356vfhv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11657@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.