all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: acm@muc.de, 74382@debbugs.gnu.org
Subject: bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer`
Date: Wed, 11 Dec 2024 14:21:06 +0300	[thread overview]
Message-ID: <d9b6c07900ad80e41ba2c88ae5da01921f17e080.camel@yandex.ru> (raw)
In-Reply-To: <86y11jf8kd.fsf@gnu.org>

(sorry, forgot to click "reply all", resending)

On related note, I am wondering if it may be better to compile `COMPILE_FIRST` files
all at once?

I haven't found any robust way to measure building time of COMPILE_FIRST-only files
as part of the build system, via some sort of invocation like `make -C lisp
SOMETHING`.

So instead I tested by invoking buliding command manually from the `build/lisp` dir
like they would be invoked by Make. And I found x2.5 improvement in build time!

Testing old behavior:

    $ find ../../ -type f -name "*.elc" -delete
    $ time for f in ../../lisp/emacs-lisp/macroexp.el ../../lisp/emacs-lisp/cconv.el ../../lisp/emacs-lisp/byte-opt.el ../../lisp/emacs-lisp/bytecomp.el ../../lisp/emacs-lisp/comp.el ../../lisp/emacs-lisp/comp-cstr.el ../../lisp/emacs-lisp/comp-common.el ../../lisp/emacs-lisp/comp-run.el; do ../src/bootstrap-emacs -batch --no-site-file --no-site-lisp -l comp -f batch-byte-compile $f; done

    real    1m38.932s
    user    1m38.684s
    sys     0m0.116s

Testing "compile all at once":

    $ find ../../ -type f -name "*.elc" -delete
    $ time ../src/bootstrap-emacs -batch --no-site-file --no-site-lisp -l comp -f batch-byte-compile ../../lisp/emacs-lisp/macroexp.el ../../lisp/emacs-lisp/cconv.el ../../lisp/emacs-lisp/byte-opt.el ../../lisp/emacs-lisp/bytecomp.el ../../lisp/emacs-lisp/comp.el ../../lisp/emacs-lisp/comp-cstr.el ../../lisp/emacs-lisp/comp-common.el ../../lisp/emacs-lisp/comp-run.el

    real    0m39.970s
    user    0m39.896s
    sys     0m0.024s






  parent reply	other threads:[~2024-12-11 11:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 15:11 bug#74382: `compile-first` Make rule is no longer using `load-prefer-newer` Konstantin Kharlamov
2024-11-16 16:27 ` Eli Zaretskii
2024-12-11 11:19   ` Konstantin Kharlamov
2024-12-11 15:41     ` Eli Zaretskii
2024-12-11 11:21   ` Konstantin Kharlamov [this message]
2024-11-16 16:53 ` Alan Mackenzie
2024-11-16 17:45   ` Konstantin Kharlamov
2024-11-16 18:38     ` Eli Zaretskii
2024-11-16 18:43       ` Konstantin Kharlamov
2024-11-16 20:00         ` Eli Zaretskii
2024-11-16 22:54           ` Konstantin Kharlamov
2024-11-17  6:44             ` Eli Zaretskii
2024-11-17 15:31               ` Konstantin Kharlamov
2024-11-17  7:25     ` Gerd Möllmann
2024-11-17 15:21       ` Konstantin Kharlamov
2024-11-17 15:37         ` Eli Zaretskii
2024-11-17 15:43           ` Konstantin Kharlamov
2024-11-17 15:53             ` Eli Zaretskii
2024-11-17 16:04               ` Konstantin Kharlamov
2024-11-17 16:29                 ` Eli Zaretskii
2024-11-17 16:46                   ` Konstantin Kharlamov
2024-11-17 17:09                     ` Eli Zaretskii
2024-11-17 17:24                       ` Konstantin Kharlamov
2024-11-18  4:06                 ` Gerd Möllmann
2024-11-18  6:19                   ` Konstantin Kharlamov
2024-11-18 10:05                   ` Konstantin Kharlamov
2024-11-18 12:59                     ` Eli Zaretskii
2024-11-18 13:12                       ` Konstantin Kharlamov
2024-11-18 13:38                         ` Eli Zaretskii
2024-12-07 11:58                           ` Eli Zaretskii
2024-11-17 15:43         ` Gerd Möllmann

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9b6c07900ad80e41ba2c88ae5da01921f17e080.camel@yandex.ru \
    --to=hi-angel@yandex.ru \
    --cc=74382@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.