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: Thu, 16 Aug 2018 16:26:32 +0300 Message-ID: <83in4aigs7.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> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1534425960 31741 195.159.176.226 (16 Aug 2018 13:26:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 16 Aug 2018 13:26:00 +0000 (UTC) Cc: eggert@cs.ucla.edu, dancol@dancol.org, emacs-devel@gnu.org To: Tom Tromey Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 16 15:25:55 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 1fqIHj-000866-9q for ged-emacs-devel@m.gmane.org; Thu, 16 Aug 2018 15:25:55 +0200 Original-Received: from localhost ([::1]:55615 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fqIJp-0005M2-Pp for ged-emacs-devel@m.gmane.org; Thu, 16 Aug 2018 09:28:05 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55985) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fqIIb-0004zl-UF for emacs-devel@gnu.org; Thu, 16 Aug 2018 09:26:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fqIIX-0004fU-HT for emacs-devel@gnu.org; Thu, 16 Aug 2018 09:26:49 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fqIIX-0004fG-Di; Thu, 16 Aug 2018 09:26:45 -0400 Original-Received: from [176.228.60.248] (port=2781 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fqIIW-0007SK-HE; Thu, 16 Aug 2018 09:26:44 -0400 In-reply-to: <87bma3i26m.fsf@tromey.com> (message from Tom Tromey on Wed, 15 Aug 2018 18:29:37 -0600) 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:228588 Archived-At: > From: Tom Tromey > Cc: Paul Eggert , dancol@dancol.org, tom@tromey.com, emacs-devel@gnu.org > Date: Wed, 15 Aug 2018 18:29:37 -0600 > > That said I don't think it is a very important issue, I think primarily > because interested users can port the JIT as needed. Only if they are _very_ interested, and have the knowledge/talent to do that. > Eli> That doesn't mean we want to have predictably bad performance, but it > Eli> does mean that we should choose our JIT library so that it doesn't > Eli> suffer from such issues. > > There is no JIT library that supports everything. OK, let me rephrase: we should choose our JIT library so that it suffers as little as possible from such issues. > So, if this is the idea, then I fear Emacs will never have a JIT. I don't think this is the idea. I think the idea is to strive to support as many popular platforms as we can. > 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.