From: Robert Pluim <rpluim@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>,
emacs-devel@gnu.org
Subject: Re: Emacs Lisp JIT Compiler
Date: Mon, 10 Sep 2018 13:15:08 +0200 [thread overview]
Message-ID: <87a7op38oz.fsf@gmail.com> (raw)
In-Reply-To: <20180910110336.scb7spl7lnmn62ar@Ergus> (Ergus's message of "Mon, 10 Sep 2018 13:03:36 +0200")
Ergus <spacibba@aol.com> writes:
> Hi!
>
> Sorry for the bother, but I am very interested in this kind of features!
>
> I have 2 simple yes/not questions:
>
> 1) Any progress in the JIT work?
Depends what you mean by progress. As far as I can tell the
feature/libjit branch compiles and runs OK.
> 2) Do you think we will see it soon in the next release or year for example?
>
Schedules are variable. Help appreciated :-)
> And an extra if you have some more time to reply.
>
> 3) I saw that the option to translate Lisp code into C and compile it is
> not considered; but I couldn't understand why and how is it better to
> use libJIT than a native compiler+binutils. Lisp-c or equivalents could
> work to distribute all the emacs internal functions already compiled but
> maybe the advanced users could enable it as an experimental feature for
> his own functions (with some configuration). Also consider the
> pedagogical value of this translator's code and the potential use cases.
Translating the lisp code into C requires the presence of a C
compiler/linker, so itʼs something that can be done by an emacs
developer, but someone using a pre-compiled emacs would not
necessarily have those tools installed. With libjit everybody would
get the benefit.
Of course, you could do both: compile the lisp shipped with emacs into
C, and support libjit, although the last time I looked at
el-compilador it didnʼt support elisp fully yet.
Robert
next prev parent reply other threads:[~2018-09-10 11:15 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 4:01 Emacs Lisp JIT Compiler Tom Tromey
2018-08-13 5:37 ` Paul Eggert
2018-08-13 15:15 ` Tom Tromey
2018-08-14 0:16 ` Tom Tromey
2018-08-14 20:11 ` Daniel Colascione
2018-08-14 20:55 ` Paul Eggert
2018-08-14 21:03 ` Daniel Colascione
2018-08-14 22:38 ` Paul Eggert
2018-08-15 16:41 ` Eli Zaretskii
2018-08-15 17:16 ` Paul Eggert
2018-08-15 17:47 ` Eli Zaretskii
2018-08-16 0:29 ` Tom Tromey
2018-08-16 13:26 ` Eli Zaretskii
2018-08-16 15:43 ` Daniel Colascione
2018-08-16 16:22 ` Andreas Schwab
2018-08-19 18:17 ` Tom Tromey
2018-08-19 19:00 ` Eli Zaretskii
2018-08-19 19:16 ` Tom Tromey
2018-08-19 20:23 ` Stefan Monnier
2018-08-18 10:10 ` Steinar Bang
2018-08-18 11:31 ` Eli Zaretskii
2018-08-19 10:00 ` Robert Pluim
2018-08-19 15:01 ` Eli Zaretskii
2018-08-19 15:26 ` Tom Tromey
2018-08-23 0:47 ` Tom Tromey
2018-08-23 16:48 ` Eli Zaretskii
2018-08-24 17:54 ` Tom Tromey
2018-08-24 20:23 ` Eli Zaretskii
2018-08-24 21:03 ` Tom Tromey
2018-08-25 6:51 ` Eli Zaretskii
2018-09-10 11:03 ` Ergus
2018-09-10 11:15 ` Robert Pluim [this message]
2018-09-10 11:53 ` Tom Tromey
2018-09-12 13:37 ` Robert Pluim
2018-09-13 4:32 ` Tom Tromey
2018-08-16 0:03 ` Tom Tromey
2018-08-16 2:45 ` Eli Zaretskii
2018-08-16 18:07 ` Eli Zaretskii
2018-08-13 13:50 ` T.V Raman
2018-08-13 15:18 ` Tom Tromey
2018-08-13 15:23 ` T.V Raman
2018-08-13 15:15 ` Eli Zaretskii
2018-08-20 21:54 ` John Wiegley
2018-08-13 23:31 ` Richard Stallman
2018-08-13 23:51 ` Tom Tromey
2018-08-16 2:42 ` Richard Stallman
2018-08-15 0:21 ` Clément Pit-Claudel
2018-08-16 0:32 ` Tom Tromey
2018-08-16 2:14 ` Clément Pit-Claudel
-- strict thread matches above, loose matches on Subject: below --
2016-12-11 17:37 Nickolas Lloyd
2016-12-12 6:07 ` John Wiegley
2016-12-12 11:51 ` Nickolas Lloyd
2016-12-12 16:45 ` John Wiegley
2016-12-23 17:22 ` Nickolas Lloyd
2016-12-13 22:24 ` Johan Bockgård
2016-12-05 18:16 Burton Samograd
2016-12-05 18:40 ` Eli Zaretskii
2016-12-05 19:32 ` Daniel Colascione
2016-12-05 21:03 ` Burton Samograd
2016-12-06 15:54 ` Lluís
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=87a7op38oz.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=spacibba@aol.com \
--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 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.