From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: andrewjmoreton@gmail.com, 46494@debbugs.gnu.org
Subject: bug#46494: 28.0.50; [native-comp] Problems with async background compile
Date: Tue, 16 Mar 2021 20:34:36 +0200 [thread overview]
Message-ID: <83czvzdk1v.fsf@gnu.org> (raw)
In-Reply-To: <xjfv99rvy4e.fsf@sdf.org> (bug-gnu-emacs@gnu.org)
> Cc: 46494@debbugs.gnu.org
> Date: Tue, 16 Mar 2021 16:53:21 +0000
> From: Andrea Corallo via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Hi Andy,
>
> is there anything left to be done for this bug?
I'm not Andy (so let's wait for him to speak up), but here's my take.
This bug had 3 parts:
a) Bug #46256 describes problems with AOT compiled native-comp emacs not
finding prebuilt .eln files when built for mingw64 64bit on Windows.
As a result, emacs complains with an echo area warning for every .eln
file that it cannot find in the expected location.
The stream of frequent warnings that causes make emacs mostly
unresponsive to user input.
b) The "background" async compilation of .eln files is CPU intensive and
somewhat slow. The default settings run a compile on every available
core, which is unfriendly for other workloads running on the same
machine.
It would be helpful to users to have a command to show the state of
the async background compilation, including the running compile
processes and the queue of pending compilation requests.
c) Quitting emacs when async compilation processes are running sometimes
causes crashes in the compile processes, which show the emacs abort
dialog (once for each async process). The dialogs disappear after a
short delay (presumably due to the parent emacs having exited).
c) Has been solved.
b) doesn't seem to be a problem IME, we use half the cores, and
there's a way to customize that number
a) I didn't see at all, so I think it's also solved.
next prev parent reply other threads:[~2021-03-16 18:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 16:58 bug#46494: 28.0.50; [native-comp] Problems with async background compile Andy Moreton
2021-02-13 18:12 ` Eli Zaretskii
2021-02-13 20:20 ` Andy Moreton
2021-02-13 20:24 ` Eli Zaretskii
2021-02-14 8:01 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-14 15:31 ` Eli Zaretskii
2021-02-14 18:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-14 19:11 ` Eli Zaretskii
2021-02-20 10:37 ` Eli Zaretskii
2021-02-20 12:09 ` Andy Moreton
2021-02-20 12:54 ` Eli Zaretskii
2021-02-20 16:40 ` Andy Moreton
2021-02-20 16:54 ` Eli Zaretskii
2021-02-20 17:30 ` Andy Moreton
2021-02-20 17:37 ` Eli Zaretskii
2021-03-07 14:34 ` Eli Zaretskii
2021-03-08 0:19 ` Andy Moreton
2021-03-08 3:27 ` Eli Zaretskii
2021-02-21 21:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 3:28 ` Eli Zaretskii
2021-02-22 19:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 16:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 18:34 ` Eli Zaretskii [this message]
2021-03-16 20:10 ` Andy Moreton
2021-03-16 20:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83czvzdk1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46494@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=andrewjmoreton@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).