unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Ahead of time compilation?
Date: Sat, 15 Sep 2018 17:33:50 -0400	[thread overview]
Message-ID: <20180915173350.2fbaa8c8@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <8336ubjli4.fsf@gnu.org>

On Sat, 15 Sep 2018 09:57:39 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 14 Sep 2018 18:16:36 -0400
> > From: "Perry E. Metzger" <perry@piermont.com>
> > 
> > Given the recent JIT discussion, it occurs to me that a large
> > fraction of the elisp infrastructure in the average emacs is the
> > stuff that gets slurped in and undumped. Perhaps all that stuff
> > could get ahead of time compiled before undump for performance?
> > Build time isn't nearly as relevant for me as speed during
> > execution, and on platforms that don't have the infra, the
> > interpreter could continue to be use for that stuff.  
> 
> IMO, before we decide to do this, we should convince ourselves that
> JIT in the libjit branch indeed speeds up things significantly
> enough for us to bother doing the above.

Naturally. If it isn't actually a significant improvement there's no
point.

Perry
-- 
Perry E. Metzger		perry@piermont.com



      reply	other threads:[~2018-09-15 21: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
2018-09-15  6:57 ` Eli Zaretskii
2018-09-15 21:33   ` Perry E. Metzger [this message]

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=20180915173350.2fbaa8c8@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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).