From: "Perry E. Metzger" <perry@piermont.com>
To: Tom Tromey <tom@tromey.com>
Cc: emacs-devel@gnu.org
Subject: Re: Ahead of time compilation?
Date: Fri, 14 Sep 2018 19:52:33 -0400 [thread overview]
Message-ID: <20180914195233.4141821d@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <875zz73ee4.fsf@tromey.com>
On Fri, 14 Sep 2018 16:25:39 -0600 Tom Tromey <tom@tromey.com> wrote:
> >>>>> "Perry" == Perry E Metzger <perry@piermont.com> writes:
>
> Perry> Given the recent JIT discussion, it occurs to me that a large
> Perry> fraction of the elisp infrastructure in the average emacs is
> Perry> the stuff that gets slurped in and undumped. Perhaps all
> Perry> that stuff could get ahead of time compiled before undump
> Perry> for performance? Build time isn't nearly as relevant for me
> Perry> as speed during execution, and on platforms that don't have
> Perry> the infra, the interpreter could continue to be use for that
> Perry> stuff.
>
> See these:
>
> https://lists.gnu.org/archive/html/emacs-devel/2018-09/msg00451.html
>
> https://lists.gnu.org/archive/html/emacs-devel/2018-08/msg00767.html
>
> There's also the unfinished el-compilador, which is a different
> expression of this idea.
I sort of meant deliberately run the JIT on *all( the elisp that gets
loaded pre-dump, and when you dump emacs, everything will be
precompiled. Or does the JIT already JIT everything that gets loaded?
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2018-09-14 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 22:16 Ahead of time compilation? Perry E. Metzger
2018-09-14 22:25 ` Tom Tromey
2018-09-14 23:52 ` Perry E. Metzger [this message]
2018-09-15 2:33 ` Tom Tromey
2018-09-15 6:57 ` Eli Zaretskii
2018-09-15 21:33 ` Perry E. Metzger
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180914195233.4141821d@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@gnu.org \
--cc=tom@tromey.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).