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: Suppressing native compilation (short and long term) Date: Sun, 23 Oct 2022 20:30:20 +0300 Message-ID: <83o7u2qwgj.fsf@gnu.org> References: <875yga36qp.fsf@no.workgroup> <83wn8qr0a3.fsf@gnu.org> <87k04qii2g.fsf@no.workgroup> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27812"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, akrl@sdf.org To: Gregor Zattler Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 24 06:38:03 2022 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 1ompDv-00073C-Pf for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Oct 2022 06:38:03 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1omnEf-0003DB-VR; Sun, 23 Oct 2022 22:30:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1omeoi-0001Nc-Az for emacs-devel@gnu.org; Sun, 23 Oct 2022 13:31:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1omeod-0001li-Va; Sun, 23 Oct 2022 13:31:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=IvwvexmHA0KJ6qvqh/YFNSjzkdPPrqXj+9AAtHsF/Hc=; b=DSnGfc1oH3wS 7lQf4QJDdaXhVeddI4KUqyRzOxm/DTPW1eOoyNv0CTiL+1MNDfYANaTMXzVUdEjn65jzbauIMJS/y YySqeKf7Z6rLwgr5Iii44mjl9DwR1R5Ur6E8HByVLaxlQ3Ly3DtK1xxmHN6mzAtuD4kgSzdcq2cKY pA7ThTTqZhAbNh818TGHNeOeB3KQJPYsF/g9VHa0TDiMDbqFx1aT5ukGYnr6kDddhmAMQvKHeni6S HETrJDA+k91/2nc353Mf94GfevuClaq6rH8v0ohVefc0NTcA9CLAeG/U5AAzSeBzc3aY1ve6e41wd pGo9+g4xmJigu26uVAB4GQ==; Original-Received: from [87.69.77.57] (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 1omeo1-00008k-0O; Sun, 23 Oct 2022 13:30:50 -0400 In-Reply-To: <87k04qii2g.fsf@no.workgroup> (message from Gregor Zattler on Sun, 23 Oct 2022 19:08:23 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:298312 Archived-At: > From: Gregor Zattler > Cc: spwhitton@spwhitton.name, rlb@defaultvalue.org, > monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org, > akrl@sdf.org > Date: Sun, 23 Oct 2022 19:08:23 +0200 > > > Please tell the details: which files are being compiled, and whether > > do you see the corresponding *.eln files in the eln-cache afterwards. > > Once a .eln file is in the eln-cache, the next invocation should not > > re-compile the same file, it should load the compiled .eln file from > > the eln-cache. > > perhaps I misinterpreted and what I saw was the testing of > the .eln cache?: > > I did > > find "/home/grfz/.config/emacs/eln-cache/" "/home/grfz/src/emacs-master-next/native-lisp/" -type f | xargs -r ls -Altr > /tmp/before > > > > while sleep 1 ; do ps -eo pid,tty,stat,user,group,etime,time,cgroup,args fax >> faxme; done # while emacs started > > find "/home/grfz/.config/emacs/eln-cache/" "/home/grfz/src/emacs-master-next/native-lisp/" -type f | xargs -r ls -Altr > /tmp/before ^^^^^^ I guess you mean "after", not "before"? > But file faxme contains 280 lines like this: > > /home/grfz/src/emacs-master-next/src/emacs --batch -l /tmp/emacs-async-comp-cl-lib-7Go9da.el And there's already a cl-lib-XXXXX.eln file under eln-cache? > 0 grfz@no:/tmp$ grep -o 'emacs-async-comp-.*' faxme | cut -d - -f 4- | sed -e "s/-[^-]*\.el$//" |sort -u | while read ; do grep -qs $REPLY before || echo $REPLY; done > 0 grfz@no:/tmp$ > > > So all these "emacs-async-comp-cl-lib-7Go9da.el" like files > have corresponding files in the .eln cache. > > Is it possible that it takes 150 secs to test the .eln cache? "Test" in what sense? Who do you think needs to "test" the cache? Anyway, the above is not what I meant. You present some commands and scripts, and expect me to guess what happens by showing only their results. It's very hard to analyze a problem that way. Instead, please do this: . find the latest subdirectory of the eln-cache whose name is 29.0.5-XXXX (where XXXX is some hash) and list is contents . start Emacs . use 'top' or similar command to see if async compilations are running which were started by Emacs you run above . compare the files these async compilations are compiling with what you see in that latest subdirectory of eln-cache . show the list of files that were compiled although they already had corresponding *.eln files in that subdirectory . let the compilations run to completion (use 'top' to see when there are no more compilations running) . look in the *Async-native-compile-log* buffer to see if there are any warning or error messages there; if there are, post them . kill Emacs . look into that subdirectory of the eln-cache and see whether there are any new *.eln files in it as result of the compilation One reason why Emacs could keep compiling files that already have *.eln files in the cache is because the existing *.eln files are outdated or incompatible with the Emacs binary. This happens a lot if you are using the master branch, because we make significant changes there frequently, and they require recompilation. You will in those cases see *.eln files whose base names are the same, but the hashes are different.