From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: 63871-done@debbugs.gnu.org
Subject: bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require
Date: Sat, 03 Jun 2023 16:51:48 +0300 [thread overview]
Message-ID: <83jzwk8xhn.fsf@gnu.org> (raw)
In-Reply-To: <m2mt1gn0im.fsf@MobileCat.localdomain> (message from Jimmy Yuen Ho Wong on Sat, 03 Jun 2023 14:22:41 +0100)
> From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
> Date: Sat, 03 Jun 2023 14:22:41 +0100
>
>
> Reproduction:
>
> 1. emacs -q -nsl --eval="(require 'cl-lib)"
> 2. C-x b TAB
> 3. Select *Async-native-compile-log*
> 4. The following is printed
>
> ```emacs-lisp
> Compiling /opt/local/share/emacs/29.0.91/lisp/emacs-lisp/cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...done
> Compilation finished.
> ```
>
> Expectation:
>
> This behavior is observed when any packages in ~/.emacs.d/elpa/
> autoloads and require cl-lib, org or tramp as well.
>
> The simple act of requiring a built-in Emacs package should not trigger
> a JIT native compilation on an Emacs installation built with
> `--with-native-compilation=aot`.
And it doesn't. cl-loaddefs has the "no-native-compile: t" thingy in
the file-local variables, so the native-compilation does nothing.
So I don't see any bug here, and I'm closing this bug.
next prev parent reply other threads:[~2023-06-03 13:51 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 [this message]
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
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=83jzwk8xhn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63871-done@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).