unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: "N. Jackson" <njackson@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, acorallo@gnu.org, 73303@debbugs.gnu.org
Subject: bug#73303: 30.0.91; Native compiler repeatedly interrupts at random moments
Date: Tue, 17 Sep 2024 20:10:23 +0000	[thread overview]
Message-ID: <87msk611ow.fsf@posteo.net> (raw)
In-Reply-To: <87a5g6yu5s.fsf@Phoenix> (N. Jackson's message of "Tue, 17 Sep 2024 19:09:03 +0000")

"N. Jackson" <njackson@posteo.net> writes:

> At 18:46 +0000 on Tuesday 2024-09-17, Philip Kaludercic wrote:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> 2. When the package system installs/updates a package, does it
>>>> natively compile the files at the same time as it byte compiles
>>>> them?
>>>
>>> I'm not sure, but I think it doesn't.  Philip, can you answer that?
>>
>> My understanding: Native compilation build on byte-compilation,
>> and all packages are byte-compiled.  If `package-native-compile'
>> is enabled (which is not the case by default), then the package is
>> immediately compiled using native-compilation as well.  This
>> applies both to installing packages and upgrading them.
>
> Shouldn't this be on by default now that native compilation is
> enabled by default?  After all, if Emacs is going to be byte
> compiling the files anyway, it might as well native compile them at
> the same time and get any issues out of the way while the user's
> mind is in working-with-packages mode.

I have no opinion on this, and as I don't build Emacs with native
compilation I cannot try it out either.

>> I don't know if the native compiler will detect .elc files
>> automatically and compile them at some later point.
>
> When they are loaded, presumably?

Right, Eli confirms this below.

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: "N. Jackson" <njackson@posteo.net>,  73303@debbugs.gnu.org,
>>   acorallo@gnu.org
>> Date: Tue, 17 Sep 2024 18:46:10 +0000
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> 2. When the package system installs/updates a package, does it
>> >> natively compile the files at the same time as it byte compiles
>> >> them?
>> >
>> > I'm not sure, but I think it doesn't.  Philip, can you answer that?
>> 
>> My understanding: Native compilation build on byte-compilation, and all
>> packages are byte-compiled.  If `package-native-compile' is enabled
>> (which is not the case by default), then the package is immediately
>> compiled using native-compilation as well.
>
> OK, so this means the OP will have to enable native compilation by
> customizing package-native-compile.

I haven't read through the entire thread, but it sounds like a possible
solution.

>> I don't know if the native compiler will detect .elc files
>> automatically and compile them at some later point.
>
> It will, but only when Emacs loads these .elc files.

-- 
	Philip Kaludercic on siskin





  reply	other threads:[~2024-09-17 20:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 18:14 bug#73303: 30.0.91; Native compiler repeatedly interrupts at random moments N. Jackson
2024-09-16 18:42 ` Eli Zaretskii
2024-09-16 19:27   ` Andrea Corallo
2024-09-18  0:43     ` N. Jackson
     [not found]   ` <87plp2mhj1.fsf@moondust.awandering>
2024-09-17 15:59     ` Eli Zaretskii
2024-09-17 18:46       ` Philip Kaludercic
2024-09-17 19:09         ` N. Jackson
2024-09-17 20:10           ` Philip Kaludercic [this message]
2024-09-24 19:13           ` Andrea Corallo
2024-09-17 19:09         ` Eli Zaretskii
2024-09-17 20:09       ` N. Jackson
2024-09-18 11:29         ` Eli Zaretskii
2024-09-24 19:10       ` Andrea Corallo
2024-09-25 11:15         ` Eli Zaretskii
2024-09-25 18:47           ` Andrea Corallo
2024-10-19  6:58             ` Eli Zaretskii
2024-10-22 16:29               ` Andrea Corallo
2024-10-23  7:04                 ` Eli Zaretskii
2024-10-23  7:44                   ` Andrea Corallo
2024-09-17 16:01   ` N. Jackson

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=87msk611ow.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=73303@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=njackson@posteo.net \
    /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).