From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 23967@debbugs.gnu.org
Subject: bug#23967: 25.1.50; Slow compilation of ns-win.el
Date: Wed, 13 Jul 2016 17:55:17 +0300 [thread overview]
Message-ID: <83bn21a8q2.fsf@gnu.org> (raw)
In-Reply-To: <m3a8hlhgs6.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 13 Jul 2016 14:19:21 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 13 Jul 2016 14:19:21 +0200
>
> I've been looking slightly at why "make -j8" isn't as parallel as you'd
> expect, and in my tests it's because one single .el compilation job is
> weirdly slow.
>
> To test:
>
> If I say "make bootstrap" (to get rid of everything) and then halt the
> compilation after it's made bootstrap-emacs
>
> [larsi@stories ~/src/emacs/trunk/lisp]$ time ../src/bootstrap-emacs -batch --no-site-file --no-site-lisp --eval "(setq load-prefer-newer t)" -l bytecomp -f byte-compile-refresh-preloaded -f batch-byte-compile ../lisp/term/ns-win.el
>
> real 0m44.097s
> user 0m44.156s
> sys 0m0.012s
>
> 44 seconds to compile it. From stracing, the thing it says before it
> ... doesn't say anything for half a minute is:
>
> readlinkat(AT_FDCWD, "/home/larsi/src/emacs/trunk/lisp/international/uni-decomposition.el", 0x7fff42af6240, 1024) = -1 EINVAL (Invalid argument)
>
> So... er... it has something to do with Unicode?
>
> This may not be a bug or anything, but it's perhaps something that
> should be looked at to speed up the initial Emacs compilation.
This is a known problem. The culprit is ucs-normalize.el
(uni-decomposition is loaded when ucs-normalize is compiled). It
takes a long time to compile even with Emacs that already has the
byte-compiled byte-compiler loaded into it. When compiling
ucs-normalize with an interpreted byte-compiler, it takes ages (11 min
on my Core i7). And since ucs-normalize is now preloaded on OS X, we
compile it with the interpreted byte-compiler, as we do with any other
file that is preloaded on _some_ platform.
Patches to solve this conundrum in some way are welcome.
next prev parent reply other threads:[~2016-07-13 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 12:19 bug#23967: 25.1.50; Slow compilation of ns-win.el Lars Ingebrigtsen
2016-07-13 14:55 ` Eli Zaretskii [this message]
2016-07-13 21:15 ` Noam Postavsky
2016-07-14 14:54 ` Eli Zaretskii
2016-07-15 3:22 ` npostavs
2016-07-15 7:21 ` Eli Zaretskii
2016-07-16 2:46 ` npostavs
2016-07-16 6:43 ` Eli Zaretskii
2016-07-16 17:03 ` npostavs
2016-07-16 17:20 ` Lars Ingebrigtsen
2016-07-17 16:20 ` npostavs
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=83bn21a8q2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23967@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).