From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Native compile: excessive recompilation? Date: Mon, 17 May 2021 19:27:02 +0000 Message-ID: References: <87a6otmba5.fsf@md5i.com> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25932"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Michael Welsh Duggan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 17 21:32:38 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 1liiyk-0006UO-Ha for ged-emacs-devel@m.gmane-mx.org; Mon, 17 May 2021 21:32:38 +0200 Original-Received: from localhost ([::1]:53488 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1liiyj-0008My-KL for ged-emacs-devel@m.gmane-mx.org; Mon, 17 May 2021 15:32:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53606) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1liitO-0004Xw-6M for emacs-devel@gnu.org; Mon, 17 May 2021 15:27:06 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:50626) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1liitM-0004Vb-E4 for emacs-devel@gnu.org; Mon, 17 May 2021 15:27:05 -0400 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 14HJR2WA003184 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 17 May 2021 19:27:02 GMT In-Reply-To: <87a6otmba5.fsf@md5i.com> (Michael Welsh Duggan's message of "Mon, 17 May 2021 15:05:06 -0400") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org 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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no 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:269424 Archived-At: Michael Welsh Duggan writes: > I, from scratch, built Emacs with native compilation and built and > installed using NATIVE_FULL_AOT=1. There is indeed a > /usr/local/lib/emacs/28.0.50/native-lisp dir with a directory that > contains the natively-compiled files. However, if I start emacs, even > with -Q, from a fresh user, files get compiled and put into the user > native compilation cache (~/.emacs.d/eln-cache/...). Has anyone else > noticed this? Or have I just made a mistake somewhere when testing > this? > > If I use emacs -Q and do `C-h i', I get compilations for the following > files: > > bytecomp-12882072-ffdd30ae.eln comp-cstr-ef162ef7-c492cd97.eln > byte-opt-9c5f25f5-b7c94b77.eln gv-e0cf7478-eac584a4.eln > cconv-3b1f1f98-ac4628a4.eln help-mode-d4dbae3d-034e8cf5.eln > cl-extra-d7051cba-ff815ded.eln info-ce12c0ca-3d2b00fd.eln > cl-lib-8b938900-fbcee53d.eln rx-627d8c83-18b6598f.eln > cl-macs-7ae82f81-d9748b96.eln seq-c314b42f-4e726806.eln > cl-seq-f464c4e2-95d0eb23.eln subr-x-02dfef32-04f2924b.eln > comp-7672a6ed-56d0b5ab.eln warnings-28e75f4d-c98d4e00.eln > > I would have thought that it would use the ones in > /usr/local/lib/emacs/28.0.50/native-lisp instead of recompiling them? > If it can be confirmed that this is a bug, I'll submit a proper bug > report. Hi Michael, please open bug with M-x report-emacs-bug so we more details on your build and we can handle the bug in the bug tracker. Thanks Andrea