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:14:29 +0300 [thread overview]
Message-ID: <83edms8wfu.fsf@gnu.org> (raw)
In-Reply-To: <055568b9-9c09-4d1f-b040-4518a9819271@Spark> (message from Jimmy Wong on Sat, 3 Jun 2023 15:05:06 +0100)
> Date: Sat, 3 Jun 2023 15:05:06 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> Cc: 63871-done@debbugs.gnu.org
>
> When there’s a package or a file that should not be natively compiled, there should be a global
> blacklist variable that controls that instead of relying on a file local variable in order to short circuit this
> behavior.
We decided against that. (A blacklist would unnecessarily complicate
any changes in our decisions which file to compile and which not to
compile.) We think what we have now is perfectly fine. I still don't
understand why you see a problem there. It's perhaps unexpected, but
that's all. It's a buffer users normally don't need to look into.
The alternatives are worse, sometimes much worse.
next prev parent reply other threads:[~2023-06-03 14:14 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
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 [this message]
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=83edms8wfu.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).