From: Tom Tromey <tom@tromey.com>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: Tom Tromey <tom@tromey.com>, emacs-devel@gnu.org
Subject: Re: Ahead of time compilation?
Date: Fri, 14 Sep 2018 20:33:51 -0600 [thread overview]
Message-ID: <878t43sd4g.fsf@tromey.com> (raw)
In-Reply-To: <20180914195233.4141821d@jabberwock.cb.piermont.com> (Perry E. Metzger's message of "Fri, 14 Sep 2018 19:52:33 -0400")
>>>>> "Perry" == Perry E Metzger <perry@piermont.com> writes:
Perry> On Fri, 14 Sep 2018 16:25:39 -0600 Tom Tromey <tom@tromey.com> wrote:
Perry> I sort of meant deliberately run the JIT on *all( the elisp that gets
Perry> loaded pre-dump, and when you dump emacs, everything will be
Perry> precompiled. Or does the JIT already JIT everything that gets loaded?
Oh, sorry, I misunderstood.
Right now the JIT always jits everything it can. This isn't ideal
though. There was a subthread about this.
I like your idea. One problem is that the portable dumper might
conflict with it. The main issue is that the JIT, currently (there are
maybe some decisions to be made here around compiling closures) bakes in
references to objects in the constant pool. (This is one reason that
the JIT code is stuck into the bytecode vector: it ties the lifetimes
together.) But, with the portable dumper, objects are "reinflated" at
startup, so this wouldn't work. (This is basically the same problem
faced by the AOT compiler.)
FWIW libjit claims to be able to write out an ELF but that isn't
actually implemented. And anyway it isn't the main problem I think.
Tom
next prev parent reply other threads:[~2018-09-15 2:33 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
2018-09-15 2:33 ` Tom Tromey [this message]
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=878t43sd4g.fsf@tromey.com \
--to=tom@tromey.com \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.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).