From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: emacs-devel@gnu.org
Subject: Re: An idea, now that we have dynamic loading
Date: Mon, 14 May 2018 15:44:15 -0600 [thread overview]
Message-ID: <87o9hhhpzk.fsf@tromey.com> (raw)
In-Reply-To: <m2k1sbckw8.fsf@newartisans.com> (John Wiegley's message of "Thu, 10 May 2018 13:31:51 -0700")
>>>>> "John" == John Wiegley <johnw@gnu.org> writes:
>>>>> "TT" == Tom Tromey <tom@tromey.com> writes:
TT> https://github.com/tromey/el-compilador
TT> This still has a bunch of bugs but it has successfully turned some elisp
TT> into C. I have an emacs branch where I replaced some of the code in subr.c
TT> with elisp.
John> Very nice! This is just what I was thinking of, so what do you need to help
John> this project mature?
I think the main thing is feeling like it matters. One of my long-term
goals was to have more of Emacs be written in Emacs Lisp, and this was a
supporting technology for that. (Other pieces were the FFI and gcc-jit
wrappers.)
However when hacking on it I ended up taking two different tacks: one
was rewriting bits of the C core in elisp; and the other was trying to
compile bits of elisp (say, stuff from subr.el or something) to C. It
wasn't clear to me which of these was more fruitful.
Anyway, the backend has some bugs, and it generates "Emacs C core"-style
C code, not "Emacs dynamic module"-style C code.
If you're just interested in performance, though, maybe my JIT is a
better choice. I haven't tried submitting the JIT here, yet, mainly
because there's still one more feature I want to finish (improved
calling convention, plus maybe inlining); but also because Stefan
pointed out a very interesting JIT paper to me, which I think would
require a ground-up rewrite (avoiding libjit).
Tom
next prev parent reply other threads:[~2018-05-14 21:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 1:44 An idea, now that we have dynamic loading John Wiegley
2018-05-06 2:25 ` Óscar Fuentes
2018-05-10 12:45 ` Siraphob (Ben) Phipathananunth
2018-05-10 20:31 ` John Wiegley
2018-05-11 6:11 ` Eli Zaretskii
2018-05-11 7:56 ` John Wiegley
2018-05-11 14:59 ` Siraphob (Ben) Phipathananunth
2018-05-11 15:02 ` Eli Zaretskii
2018-05-11 15:22 ` An Emacs benchmarking suite (was: An idea, now that we have dynamic loading) Siraphob (Ben) Phipathananunth
2018-05-11 17:38 ` Eli Zaretskii
2018-05-14 11:37 ` An Emacs benchmarking suite Phillip Lord
2018-05-14 16:18 ` Eli Zaretskii
2018-05-14 16:30 ` Stefan Monnier
2018-05-15 13:24 ` Phillip Lord
2018-05-10 13:58 ` An idea, now that we have dynamic loading Tom Tromey
2018-05-10 20:31 ` John Wiegley
2018-05-14 21:44 ` Tom Tromey [this message]
2018-05-14 23:36 ` John Wiegley
2018-05-21 21:13 ` Tom Tromey
2018-05-22 3:23 ` John Wiegley
2018-05-22 4:20 ` Tom Tromey
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=87o9hhhpzk.fsf@tromey.com \
--to=tom@tromey.com \
--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 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.