unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lally Singh <lally.singh@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs Lisp's future (was: Guile emacs thread (again))
Date: Tue, 16 Sep 2014 22:57:31 -0400	[thread overview]
Message-ID: <CAFjuTDBu4uCjTo3MScqTnXv97p94hLqHSu1j+oe4QGdPgKb6=A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

So if this a runtime system issue, what about elisp on LLVM?  Let the LLVM
project handle the backend and performance issues, and emacs can maintain
one language frontend.  There are plenty of people working on that, so
emacs can ride that for almost free.

I'm assuming that there are reasons why it doesn't work, as someone
(apparently) did the work some time ago:
https://github.com/boostpro/emacs-llvm-jit  Perhaps it just needs a little
TLC?

[-- Attachment #2: Type: text/html, Size: 577 bytes --]

             reply	other threads:[~2014-09-17  2:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  2:57 Lally Singh [this message]
2014-09-17 11:01 ` Emacs Lisp's future (was: Guile emacs thread (again)) Tom
2014-09-17 12:28   ` Emacs Lisp's future Stefan Monnier
2014-09-17 12:58     ` Tom
2014-09-17 13:39       ` Óscar Fuentes
2014-09-17 14:15         ` Tom
2014-09-17 11:43 ` Emacs Lisp's future (was: Guile emacs thread (again)) Richard Stallman
2014-09-17 14:21   ` Lally Singh
2014-09-17 15:04     ` Emacs Lisp's future Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2014-09-17  8:22 Emacs Lisp's future (was: Guile emacs thread (again)) Nic Ferrier
2014-09-17  7:38 Kristian Nygaard Jensen
2014-09-11 16:29 Guile emacs thread (again) Christopher Allan Webber
2014-09-16 15:50 ` Emacs Lisp's future (was: Guile emacs thread (again)) Stefan Monnier
2014-09-16 16:03   ` Lennart Borgman
2014-09-17 18:24     ` Jorgen Schaefer
2014-09-17 19:25       ` Lally Singh
2014-09-18  2:07       ` Alexis
2014-09-18  8:43     ` Emilio Lopes
2014-09-16 16:09   ` Eli Zaretskii
2014-09-16 16:54   ` Lars Brinkhoff

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='CAFjuTDBu4uCjTo3MScqTnXv97p94hLqHSu1j+oe4QGdPgKb6=A@mail.gmail.com' \
    --to=lally.singh@gmail.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 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).