From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: Native compilation: the bird-eye view Date: Wed, 03 Jun 2020 14:23:21 +0000 Message-ID: References: <83o8qocd32.fsf@gnu.org> <83ftbzdewp.fsf@gnu.org> <83blmndbpo.fsf@gnu.org> <838shrdb1c.fsf@gnu.org> <837dxbd93b.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="64561"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cc: Eli Zaretskii , Paul Eggert , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jun 03 16:24:27 2020 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 1jgUJf-000GfD-7W for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Jun 2020 16:24:27 +0200 Original-Received: from localhost ([::1]:49328 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jgUJe-00017W-5L for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Jun 2020 10:24:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60202) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jgUIo-0007jZ-Sy for emacs-devel@gnu.org; Wed, 03 Jun 2020 10:23:36 -0400 Original-Received: from mx.sdf.org ([205.166.94.20]:51161) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jgUIn-0002JO-0u; Wed, 03 Jun 2020 10:23:34 -0400 Original-Received: from sdf.org (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 053ENLPE000232 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 3 Jun 2020 14:23:22 GMT Original-Received: (from akrl@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 053ENLAJ013512; Wed, 3 Jun 2020 14:23:21 GMT In-Reply-To: (Stefan Monnier's message of "Tue, 02 Jun 2020 11:16:46 -0400") Received-SPF: pass client-ip=205.166.94.20; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/03 10:23:30 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action 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:251809 Archived-At: Stefan Monnier writes: > This is OK but doubles the length of the effective `load-path`. > Another option would be to use > > ~/.emacs.d/eln-cache/eln-x86_64-pc-linux-gnu-d241bf45dde51f21/.eln > > where is a hash of the corresponding .el(c) file name. Similarly, instead of > > /bar/foo.el => /bar/eln-x86_64-pc-linux-gnu-d241bf45dde51f21/foo.eln > > we would store those compiled files to a "global eln-cache" > > /bar/foo.el => /usr/lib/eln-cache/eln-x86_64-pc-linux-gnu-d241bf45dde51f21/.eln > > So we'd have a `eln-cache-path` where to search for those files and when > loading a file we'd first look for the .el file in `load-path` and once > found, we'd look inside `eln-cache-path` to see if that file has > a compiled version available. `eln-cache-path` would be expected to be > short (2 entries in the typical case). This is a good idea. My concerns are on how the user would interact with this cache ex: searching if a given eln exists, what's its date, removing one eln etc. Should the user goes always through an API we provide? Or do we want have everything 100% transparent? Andrea -- akrl@sdf.org