From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jimmy Wong Newsgroups: gmane.emacs.bugs Subject: bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require Date: Sat, 3 Jun 2023 15:15:05 +0100 Message-ID: References: <83jzwk8xhn.fsf@gnu.org> <9cb1886a-7173-4d27-bac6-183069875db8@Spark> <83fs788wko.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="647b4afe_1cac62c6_d2d7" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18188"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63871@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jun 03 16:16:14 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1q5S3C-0004Wt-Me for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 03 Jun 2023 16:16:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q5S35-0006F1-QE; Sat, 03 Jun 2023 10:16:07 -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 1q5S2z-0006Ef-Cy for bug-gnu-emacs@gnu.org; Sat, 03 Jun 2023 10:16:01 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1q5S2z-00004t-2G for bug-gnu-emacs@gnu.org; Sat, 03 Jun 2023 10:16:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q5S2y-0006rd-TO for bug-gnu-emacs@gnu.org; Sat, 03 Jun 2023 10:16:00 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jimmy Wong Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 03 Jun 2023 14:16:00 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63871 X-GNU-PR-Package: emacs Original-Received: via spool by 63871-submit@debbugs.gnu.org id=B63871.168580173523042 (code B ref 63871); Sat, 03 Jun 2023 14:16:00 +0000 Original-Received: (at 63871) by debbugs.gnu.org; 3 Jun 2023 14:15:35 +0000 Original-Received: from localhost ([127.0.0.1]:44073 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q5S2Z-0005yi-2N for submit@debbugs.gnu.org; Sat, 03 Jun 2023 10:15:35 -0400 Original-Received: from mail-wm1-f53.google.com ([209.85.128.53]:60562) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q5S2X-0005fr-5z for 63871@debbugs.gnu.org; Sat, 03 Jun 2023 10:15:33 -0400 Original-Received: by mail-wm1-f53.google.com with SMTP id 5b1f17b1804b1-3f6e13940daso31854195e9.0 for <63871@debbugs.gnu.org>; Sat, 03 Jun 2023 07:15:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685801727; x=1688393727; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:from:to:cc:subject:date:message-id:reply-to; bh=3NCZdq6TNmQ1IPfVYey8dX/4oNB0G7ADqIRYPcSPWgQ=; b=J1pTQ/MgToW9hAt/w/ueyflU1PPshM5jHeeU3naBJe0jnIK7EG1FkHTQGnqZFtm0LH FAugYX0BIYPx+LReU8XhTR4FUrUMOYmxBsryoc6EY6Q4RCLK57hsn/9uiaemCDcQ1/I8 JVQsA9krxB83c3lveJxaUHE6I6UJUKV/nX7hZS2fGsY0RoNuCSgC6la8tsV989r8CZ1K WaWmn0B1LCAQzIHgj5G37gMqG3+gw/8mvLhS/q3RUa5SpKvmu/7SxaVkiGX992xdkhpM U1fVF1xqhqHS0MLbRrFV3AGs1EM2Giecg/7Lx1ABbq9aov7MO2DQtjb6AloFxE/ckdPD /+Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685801727; x=1688393727; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3NCZdq6TNmQ1IPfVYey8dX/4oNB0G7ADqIRYPcSPWgQ=; b=GEqECKPmzbwFla404Z2ekkJiFRrGiukR+iU2TdulMDvwp9W/xwr05J6lsMJgTpIgcG /9K8lcywnDGnZ4fz23HPK+QB3W0SYWZ5vaR/26VljbRYQQqniE6C+dHFPje0kr9ZxwY5 WuH4ejGARNzcJG2GNSard7Xlufvv7iRuLcWU0BrdXEpX2Bfm7vJ7GzoZbEyoPFmLtbK+ ji0ce8NFkNkS/dfzVI8reSYTDfd/OrvxGmAt4NOdYxrajfsrPFFUAvsMhQE6dut7XLPB yXEA2hPbhmqizEm2dRBkSILPIaPmlEUThIL5NzSxlfu6vxMt7U2s+hZa/cVhh/icEdPd IlAQ== X-Gm-Message-State: AC+VfDz7hBSzmjn4YI5XrUjiucSHqbIKmBMGCQl/IOMuNumhGnCgRvuT AnyRZ56Cj5lOswbGW0H97ahsWYZRiqI= X-Google-Smtp-Source: ACHHUZ46YV9K2TT3wDs13Rfks/1aMvDGMB72soUpuyQ78AdXpp7OGiv9HMnZoy+NYGwoocDhZlZawg== X-Received: by 2002:a05:600c:22c6:b0:3f6:f2b2:15c9 with SMTP id 6-20020a05600c22c600b003f6f2b215c9mr4633780wmg.37.1685801727416; Sat, 03 Jun 2023 07:15:27 -0700 (PDT) Original-Received: from [2a01:4b00:89a0:2400:9c:6b10:100:0] ([2a01:4b00:89a0:2400:18b7:3953:b17d:de2c]) by smtp.gmail.com with ESMTPSA id 13-20020a05600c22cd00b003f709a7e46bsm8712821wmg.46.2023.06.03.07.15.26 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Jun 2023 07:15:26 -0700 (PDT) In-Reply-To: <83fs788wko.fsf@gnu.org> X-Readdle-Message-ID: c39ac55e-b797-4931-a6ee-9536f61629b3@Spark X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:262852 Archived-At: --647b4afe_1cac62c6_d2d7 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Unless you=E2=80=99ve set package-native-compile to t so you=E2=80=99ll r= arely see this buffer. Installing new packages is not a frequent operatio= n in normal Emacs usage, and when a user installs a new package and loads= it, he=E2=80=99ll expect that buffer, not when simply having a package t= hat requires that a package. On 3 Jun 2023 at 3:10 PM +0100, Eli Zaretskii , wrote: > > Date: Sat, 3 Jun 2023 15:02:18 +0100 > > =46rom: Jimmy Wong > > Cc: 63871-done=40debbugs.gnu.org > > > > The problem is this: > > > > 1 There=E2=80=99s no-native-compile:r set in the file, so a eln file = was never produced. > > 2 nativecomp does not know which file should not be compiled until it= opens the file > > 3 Whenever a require is encountered, nativecomp can=E2=80=99t find it= s eln, doesn=E2=80=99t know it can=E2=80=99t be compiled > > until it reads the file, and it can=E2=80=99t read the file until it = unzips the file. > > 4 This unnecessary work is done every time any package requires one o= f these packages that > > cannot be compiled, again and again, generating an extra buffer that = mess up the buffer orders in > > the buffer list. > > Sorry, I don't see any problem. This is normal and expected behavior, > and one more buffer cannot possibly be a problem. Especially since > that buffer will be created soon enough anyway, once you load some > previously-uncompiled package. > > I fail to understand why another buffer could be a problem. > > I don't see any bug here. --647b4afe_1cac62c6_d2d7 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Unless you=E2=80=99ve set package-native-compile to= t so you=E2=80=99ll rarely see this buffer. Installing new packages is n= ot a frequent operation in normal Emacs usage, and when a user installs a= new package and loads it, he=E2=80=99ll expect that buffer, not when sim= ply having a package that requires that a package.
On 3 Jun 2023 at 3:10 PM +0100, Eli= Zaretskii <eliz=40gnu.org>, wrote:
Date: Sat, 3 Jun 2023 15:02:18 +0100
=46rom: Jimmy Wong <wyuenho=40gmail.com>
Cc: 63871-done=40debbugs.gnu.org

The problem is this:

1 There=E2=80=99s no-native-compile:r set in the file, so a eln file was = never produced.
2 nativecomp does not know which file should not be compiled until it ope= ns the file
3 Whenever a require is encountered, nativecomp can=E2=80=99t find its el= n, doesn=E2=80=99t know it can=E2=80=99t be compiled
until it reads the file, and it can=E2=80=99t read the file until it unzi= ps the file.
4 This unnecessary work is done every time any package requires one of th= ese packages that
cannot be compiled, again and again, generating an extra buffer that mess= up the buffer orders in
the buffer list.

Sorry, I don't see any problem. This is normal and expected behavior,
and one more buffer cannot possibly be a problem. Especially since
that buffer will be created soon enough anyway, once you load some
previously-uncompiled package.

I fail to understand why another buffer could be a problem.

I don't see any bug here.
--647b4afe_1cac62c6_d2d7--