From: Lynn Winebarger <owinebar@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Loading tramp for dump goes into infinite regress
Date: Tue, 9 Aug 2022 11:55:59 -0400 [thread overview]
Message-ID: <CAM=F=bBXeNmcsLS_YN1+6f69_GgSRV74VcQOb7HWAzW=ZYjfNg@mail.gmail.com> (raw)
In-Reply-To: <87bkstzg6e.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
On Tue, Aug 9, 2022, 9:43 AM Po Lu <luangruo@yahoo.com> wrote:
> Lynn Winebarger <owinebar@gmail.com> writes:
>
> > I'm not sure you can conclude that the benefit would be minor when the
> > non-collected space is a 184MB dump file instead of a fixed pure space
> > that is 2 or 2.4MB as it is in the standard pdump.
>
> AFAIK we don't officially support any non-standard dump.
>
I'm not sure how that's relevant, but depending on what you mean by
"support", it may not be totally accurate. Aside from providing the option
of including site-load and site-init in the system build, there is the
user-level function dump-emacs-portable. It's accurate to say the
maintainers are not responsible for supporting every random set of
libraries put together in a dump. But it's also fair to say that the
impact of the system design on nonstandard user dumps is within the remit
of the maintainers as a general matter. That said, the priority of such
concerns is entirely up to the maintainers.
> At least some vestiges of the write barrier appear to be in place
> > during dump mode. I've had to make a lot of minor corrections of
> > "defconst" keymaps to defvar, for example due to pure_write_error
> > getting called. Whether that barrier is uniformly enforced or not is
> > one of the reasons I suspect this quick hack would not be sufficient.
>
> I don't think it's very well enforced. For example, any C code that
> calls XSETCAR without checking whether or not the object (i.e. the reuse
> argument to Fmatch_end) is writable will result in the invariant being
> broken.
>
True, but if all relevant mutators are effectively contained in lisp.h, the
problem of imposing a write barrier would be effectively contained. Then
it would just be a matter of determining if the cost of the write barrier
being checked at every mutation is paid for by a perceivable reduction in
gc-related pauses.
But as I said, it's just a hack I'm tempted to try. I probably won't
unless the gc pauses for this mega-dump build become intolerable.
Lynn
[-- Attachment #2: Type: text/html, Size: 3308 bytes --]
next prev parent reply other threads:[~2022-08-09 15:55 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 [this message]
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
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=bBXeNmcsLS_YN1+6f69_GgSRV74VcQOb7HWAzW=ZYjfNg@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).