From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Wong <wyuenho@gmail.com>
Cc: 63871@debbugs.gnu.org
Subject: bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require
Date: Sat, 03 Jun 2023 17:11:35 +0300 [thread overview]
Message-ID: <83fs788wko.fsf@gnu.org> (raw)
In-Reply-To: <9cb1886a-7173-4d27-bac6-183069875db8@Spark> (message from Jimmy Wong on Sat, 3 Jun 2023 15:02:18 +0100)
> Date: Sat, 3 Jun 2023 15:02:18 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> Cc: 63871-done@debbugs.gnu.org
>
> The problem is this:
>
> 1 There’s 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’t find its eln, doesn’t know it can’t be compiled
> until it reads the file, and it can’t read the file until it unzips the file.
> 4 This unnecessary work is done every time any package requires one of 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.
next prev parent reply other threads:[~2023-06-03 14:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 13:22 bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require Jimmy Yuen Ho Wong
2023-06-03 13:51 ` Eli Zaretskii
2023-06-03 13:54 ` Jimmy Wong
2023-06-03 14:09 ` Eli Zaretskii
2023-06-03 14:11 ` Jimmy Wong
2023-06-03 14:17 ` Eli Zaretskii
2023-06-03 14:02 ` Jimmy Wong
2023-06-03 14:11 ` Eli Zaretskii [this message]
2023-06-03 14:15 ` Jimmy Wong
2023-06-03 14:25 ` Eli Zaretskii
2023-06-03 14:05 ` Jimmy Wong
2023-06-03 14:14 ` Eli Zaretskii
2023-06-03 14:17 ` Jimmy Wong
2023-06-03 14:26 ` Eli Zaretskii
2023-06-03 14:50 ` Jimmy Wong
2023-06-03 15:05 ` Eli Zaretskii
2023-06-03 15:11 ` Jimmy Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fs788wko.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63871@debbugs.gnu.org \
--cc=wyuenho@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).