From: Lynn Winebarger <owinebar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andrea Corallo <akrl@sdf.org>,
Michael Albinus <michael.albinus@gmx.de>,
emacs-devel <emacs-devel@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Native-compilation build process (was Re: Loading tramp for dump goes into infinite regress)
Date: Thu, 4 Aug 2022 21:57:23 -0400 [thread overview]
Message-ID: <CAM=F=bBYKyjvWtpEQbqwySwLV3VLNJqDF8=C9xJ0XANmzAKctg@mail.gmail.com> (raw)
In-Reply-To: <CAM=F=bD53RX9v8Kt2ifAm0fQ=bO7agyuF=fCWiFhngMJwWvGKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
On Wed, Aug 3, 2022, 11:33 PM Lynn Winebarger <owinebar@gmail.com> wrote:
>
> * 698 libraries in the preloaded-file-list
> * 136 files listed in lisp.mk
> * 521 files listed in site-load.mk (the file I generate from
> site-load)
> * I'm not sure where the remainder are from
> * 426 native compilation units in "all-loaded-comp-units-h"
> * 1126 eln files under native-lisp/28.1-<hash>/preloaded - none appear
> directly in 28.1-<hash>
> * 1504 elc files under lisp
> * 1557 el files under lisp
> I'm not sure why some of the files were byte compiled but not native
> compiled (or at least, not loaded in the dump).
It was just from the way native compiled files are not tracked on the
build, and having done a pure byte-compile run to ensure everything would
have compiled dependencies.
Once touched all the source files and redumped, everything that could be
compiled was loaded as native compiled, for a total of 596 NCUs in the dump.
I will now proceed to iron out the load dependency order of the additional
libraries I have set up and compiled in site-lisp.
I found adding call-interactive to the "never-optimize" lists (one
customization variable, one hard coded list in nadvice) resolved the issue
with the runaway async subr compilation. I deleted close to 100k ELISP
files from /tmp today from jobs I killed.
Lynn
[-- Attachment #2: Type: text/html, Size: 2197 bytes --]
next prev parent reply other threads:[~2022-08-05 1:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 0:47 Loading tramp for dump goes into infinite regress Lynn Winebarger
2022-07-24 7:55 ` Michael Albinus
2022-07-24 12:05 ` Lynn Winebarger
2022-07-24 12:23 ` Eli Zaretskii
2022-07-24 13:30 ` Lynn Winebarger
2022-07-24 13:34 ` Eli Zaretskii
2022-07-24 14:05 ` Lynn Winebarger
2022-07-24 14:09 ` Eli Zaretskii
2022-07-24 14:28 ` Lynn Winebarger
2022-07-24 16:00 ` Lynn Winebarger
2022-07-24 16:20 ` Lynn Winebarger
2022-07-24 16:31 ` Eli Zaretskii
2022-07-25 12:49 ` Lynn Winebarger
2022-07-25 13:56 ` Eli Zaretskii
2022-07-26 11:24 ` Lynn Winebarger
2022-07-27 0:58 ` Lynn Winebarger
2022-07-27 2:48 ` Lynn Winebarger
2022-07-27 8:31 ` Lynn Winebarger
2022-08-09 12:29 ` Lynn Winebarger
2022-08-09 12:36 ` Po Lu
2022-08-09 13:22 ` Lynn Winebarger
2022-08-09 13:42 ` Po Lu
2022-08-09 15:55 ` Lynn Winebarger
2022-07-25 16:54 ` Stefan Monnier
2022-07-25 17:05 ` Stefan Monnier
2022-07-26 0:28 ` Lynn Winebarger
2022-07-26 1:10 ` Lynn Winebarger
2022-08-06 6:07 ` Lynn Winebarger
2022-08-06 12:57 ` Lynn Winebarger
2022-08-06 15:39 ` Lynn Winebarger
2022-08-06 20:23 ` Working fully native-compiled "mega dump" (was Re: Loading tramp for dump goes into infinite regress) Lynn Winebarger
2022-08-06 20:52 ` Lynn Winebarger
2022-07-25 20:11 ` Loading tramp for dump goes into infinite regress Andrea Corallo
2022-07-31 20:22 ` Lynn Winebarger
2022-08-03 9:58 ` Lynn Winebarger
2022-08-03 12:22 ` Eli Zaretskii
2022-08-03 14:53 ` Native-compilation build process (was Re: Loading tramp for dump goes into infinite regress) Lynn Winebarger
2022-08-03 16:15 ` Eli Zaretskii
2022-08-04 3:33 ` Lynn Winebarger
2022-08-05 1:57 ` Lynn Winebarger [this message]
2022-07-24 16:23 ` Loading tramp for dump goes into infinite regress Eli Zaretskii
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='CAM=F=bBYKyjvWtpEQbqwySwLV3VLNJqDF8=C9xJ0XANmzAKctg@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
/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).