From: akrl--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 45858@debbugs.gnu.org
Subject: bug#45858: 28.0.50; [native-comp] compilation very slow
Date: Thu, 28 Jan 2021 21:20:39 +0000 [thread overview]
Message-ID: <xjf4kj0wyfs.fsf@sdf.org> (raw)
In-Reply-To: <871reniu3r.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Thu, 14 Jan 2021 13:24:56 +0100")
Óscar Fuentes <ofv@wanadoo.es> writes:
> After starting a new instance of Emacs with an empty eln-cache,
> producing .eln files takes a long time. Any typical file takes more than
> five minutes, with some files (like lsp-protocol.el, right now)
> approaching two hours. Memory consumption is reasonable (155 MB for the
> process that is compiling lsp-protocol.el, about 60 MB for a typical
> compilation process).
>
> Right now, after 9 hours, there are 272 .eln files in the cache.
>
> The machine is a high-end desktop from 2015 and has dozens of GB of free
> memory and remains perfectly responsible, this is not the problem about
> excessive memory use that was reported previously. There is no other
> significant CPU activity.
This is behaviour is unexpected, but is kind of hard if not impossible
to guess the issue from here.
I guess both Emacs and and libgccjit are not debug build correct?
Andrea
next prev parent reply other threads:[~2021-01-28 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 12:24 bug#45858: 28.0.50; [native-comp] compilation very slow Óscar Fuentes
2021-01-28 21:20 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-01-31 2:54 ` Óscar Fuentes
2021-02-02 22:13 ` Óscar Fuentes
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=xjf4kj0wyfs.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45858@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=ofv@wanadoo.es \
/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).