From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Add a configure option for NATIVE_FULL_AOT? Date: Wed, 18 Aug 2021 16:45:42 +0300 Message-ID: <83pmua50jd.fsf@gnu.org> References: <834kbo6xm5.fsf@gnu.org> <87zgtg3x4i.fsf@wavexx.thregr.org> <83zgtg57jv.fsf@gnu.org> <87r1er3oqr.fsf@igel.home> <83lf4z6hh0.fsf@gnu.org> <83fsv75w43.fsf@gnu.org> <20210818073349.GC18126@tuxteam.de> <835yw354rb.fsf@gnu.org> <20210818133233.GA3470@tuxteam.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3269"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: tomas@tuxteam.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 18 15:47:03 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mGLuJ-0000bT-0L for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Aug 2021 15:47:03 +0200 Original-Received: from localhost ([::1]:57390 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGLuH-0006YL-Ez for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Aug 2021 09:47:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48484) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGLtF-0005sw-8W for emacs-devel@gnu.org; Wed, 18 Aug 2021 09:45:57 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47932) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mGLtE-0008Sb-Hs; Wed, 18 Aug 2021 09:45:56 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2564 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mGLt1-0006TK-E2; Wed, 18 Aug 2021 09:45:56 -0400 In-Reply-To: <20210818133233.GA3470@tuxteam.de> (tomas@tuxteam.de) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:272570 Archived-At: > Date: Wed, 18 Aug 2021 15:32:33 +0200 > From: tomas@tuxteam.de > Cc: emacs-devel@gnu.org > > > They can, and they do. See native-comp-eln-load-path. Assuming I > > understood correctly what bothers you. > > Thanks. > > I think you do. Well, I'm quite certain :) > > Then what would prevent a distribution from distributing their .eln > files to go somewhere in /usr/lib/emacs...//..., to be > overriden by the user when needed? I don't think I understand. load-path is used for only one purpose: finding Lisp files you want to load. It is not used to decide where to _write_ *.elc files. The same with native-comp-eln-load-path (but see below). So how can this variable solve the problem at hand, which is where to store *.eln files produced by compilation? We actually do use native-comp-eln-load-path to also decide where to store the *.eln files, but that uses a simplistic heuristic that treats the last element of the list specially. The heuristic is hard-coded in several places, so not easily overridden. > I've been following the native compilation threads with quite some > excitement, but I'm sure I haven't digested many "interesting" > details :) "Interesting" as in the infamous Chinese curse? It's those "interesting" details that bother me: I needed to think about them and discuss them with Andrea many times over the last months, and in many cases the issue was put to rest by considering the JIT scenario. I don't know what would have happened if we considered the AOT scenario as seriously as people want us to do now.