unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Regression in dump-emacs-portable
Date: Tue, 14 Feb 2023 18:26:07 -0500	[thread overview]
Message-ID: <CAM=F=bC7N09rChon1Hcbg__++ng0XCmBFLBx+ELXQYg4Pn2r=g@mail.gmail.com> (raw)
In-Reply-To: <83ttzocomk.fsf@gnu.org>

On Tue, Feb 14, 2023 at 9:23 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Lynn Winebarger <owinebar@gmail.com>
> > Date: Mon, 13 Feb 2023 20:13:22 -0500
> >
> > I also looked for tests of dump-emacs-portable in the test/
> > subdirectory, and grep reported nothing.  I can translate my shell
> > script into elisp to run under ERT, and add testing for each of the
> > libraries expected to be dumpable (in the sense of not requiring code
> > evaluated on load that needs to be delayed until run-time)
> > individually.  How do I submit that?  Are there any restrictions I
> > should observe?
>
> What do these tests actually test?

Whether libraries expected to be redumpable are in fact redumpable.
Almost every library in 28.2 could be redumped, excepting those which
simply failed to load for whatever reason.  Even the ones that need to
be delayed until initialization for practical reasons do not cause
dump-emacs-portable to fail.  A library changing from dumpable to
non-dumpable might be acceptable, but that change has to be known to
evaluate the tradeoff.  Additionally, whether the maximal set of files
expected to be redumpable is redumpable as a whole.  If the maximal
set can be redumped, then presumably any proper subset (closed under
require) could be as well.

Obviously someone's been optimizing something to see the maximal
redump size decrease by 45%.  The total number of libraries (excluding
the obsolete directory) appears to have decreased, but enough to
explain that much of a change in size?

Lynn



  reply	other threads:[~2023-02-14 23:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  0:51 Regression in dump-emacs-portable Lynn Winebarger
2023-02-14  1:13 ` Lynn Winebarger
2023-02-14 14:23   ` Eli Zaretskii
2023-02-14 23:26     ` Lynn Winebarger [this message]
2023-02-15 12:42       ` Eli Zaretskii
2023-02-16  9:31         ` Lynn Winebarger
2023-02-16  9:54           ` Lynn Winebarger
2023-02-16 15:05             ` Lynn Winebarger
2023-02-16 15:34               ` Eli Zaretskii
2023-02-16 23:45                 ` Lynn Winebarger
2023-02-17 13:22                   ` Lynn Winebarger
2023-02-17 14:31                     ` Eli Zaretskii
2023-02-17 23:44                       ` Lynn Winebarger
2023-02-18  7:07                         ` Eli Zaretskii
2023-02-21 14:21                           ` Lynn Winebarger
2023-02-23  2:41                             ` Lynn Winebarger
2023-02-23 13:21                 ` Lynn Winebarger
2023-02-16 15:46           ` Eli Zaretskii
2023-02-17  1:29             ` Lynn Winebarger
2023-02-17  3:19               ` Lynn Winebarger
2023-02-17  4:10               ` Lynn Winebarger
2023-02-17  5:21                 ` Po Lu
2023-02-17 12:57                   ` Lynn Winebarger
2023-02-23 15:08 ` Gregory Heytings
2023-02-23 22:32   ` Lynn Winebarger
2023-02-25  4:11     ` Richard Stallman
2023-02-25  4:11     ` Richard Stallman

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=bC7N09rChon1Hcbg__++ng0XCmBFLBx+ELXQYg4Pn2r=g@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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).