From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp JIT Compiler Date: Sat, 18 Aug 2018 14:31:58 +0300 Message-ID: <83in47gbbl.fsf@gnu.org> References: <87va8ej4o1.fsf@tromey.com> <87mutpiyz6.fsf@tromey.com> <701cd05f423e0c46595a3010f45414d0.squirrel@dancol.org> <520f536b5a603831c9a57a5f6f0978a2.squirrel@dancol.org> <83va8binu8.fsf@gnu.org> <87bma3i26m.fsf@tromey.com> <83in4aigs7.fsf@gnu.org> <86lg94htom.fsf@dod.no> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1534591848 24628 195.159.176.226 (18 Aug 2018 11:30:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 18 Aug 2018 11:30:48 +0000 (UTC) Cc: emacs-devel@gnu.org To: Steinar Bang Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 18 13:30:44 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fqzRL-0006KA-MU for ged-emacs-devel@m.gmane.org; Sat, 18 Aug 2018 13:30:43 +0200 Original-Received: from localhost ([::1]:38506 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fqzTQ-0004po-Jm for ged-emacs-devel@m.gmane.org; Sat, 18 Aug 2018 07:32:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53578) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fqzSk-0004pi-FN for emacs-devel@gnu.org; Sat, 18 Aug 2018 07:32:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fqzSh-0000uC-8K for emacs-devel@gnu.org; Sat, 18 Aug 2018 07:32:10 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:59430) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fqzSh-0000u6-4C; Sat, 18 Aug 2018 07:32:07 -0400 Original-Received: from [176.228.60.248] (port=3512 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fqzSg-0002Bz-Ne; Sat, 18 Aug 2018 07:32:07 -0400 In-reply-to: <86lg94htom.fsf@dod.no> (message from Steinar Bang on Sat, 18 Aug 2018 12:10:01 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228659 Archived-At: > From: Steinar Bang > Date: Sat, 18 Aug 2018 12:10:01 +0200 > > >>>>> Eli Zaretskii : > > >> From: Tom Tromey > > >> Now, one thing that is portable is compiling Emacs Lisp code to C. > > > That again needs a compiler and Binutils, so it suffers from the same > > drawback. > > It could be used ahead-of-time (or whatever the term is), to move emacs > code currently implemented in C to lisp. The intent is to allow Emacs to compile _any_ Lisp into native code. The main advantage of that is when the Lisp in question didn't come with the distribution. Because otherwise we could just JIT-compile everything in advance and be done. IOW, what you mention is a one-time feature, mainly useful to Emacs developers. The drawback I mentioned is for the Emacs users, and AFAIU the JIT feature mainly targets the users.