From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: An idea, now that we have dynamic loading
Date: Sun, 06 May 2018 04:25:17 +0200 [thread overview]
Message-ID: <87efipmsfm.fsf@telefonica.net> (raw)
In-Reply-To: m2fu35blrp.fsf@newartisans.com
"John Wiegley" <johnw@gnu.org> writes:
> It occurred to me today that we have tons of examples of how Lisp functions
> can be written in a flavor C. This "compilation" is typically done by hand by
> a few experts.
>
> However, what if we had a compiler from Emacs Lisp -> Lisp-flavored C, which
> could turn .el files into .c files suitable for compiling into .so's that can
> be loaded into Emacs?
Mandatory mention:
JIT Compilation for Emacs
http://tromey.com/blog/?p=982
IMHO and based on my experience with other projects, this is the way
Elisp should go for improving performance. It is dubious that the
approach you mention would be any better on terms of raw performance,
apart from decreasing load time. Anyways, if speed is really important,
nothing beats a pure C implementation.
next prev parent reply other threads:[~2018-05-06 2:25 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 [this message]
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
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=87efipmsfm.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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.