unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57035@debbugs.gnu.org
Subject: bug#57035: Support for site-load.el in native-compile dumping
Date: Sun, 7 Aug 2022 09:16:11 -0400	[thread overview]
Message-ID: <CAM=F=bBdhugCWp_j+-bC6fjoHQnkjzP3j0n6JeQ9U9hOTOmCsQ@mail.gmail.com> (raw)
In-Reply-To: <878ro02owz.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

On Sun, Aug 7, 2022, 8:55 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Lynn Winebarger <owinebar@gmail.com> writes:
>
> > +. Add a flag variable to turn off the docstring hack in lead.c once
> > loadup has been processed (or eliminate the hack entirely).
>
> The hack has been removed on the trunk.
>
> > I think that covers all the issues I dealt with.  If my employer
> > allows I can donate code to fix the purecopy issues in versions prior
> > to 29.
>
> As I think Eli has said before, changes in this area are not going to be
> backported to earlier Emacs versions, so you should just concentrate on
> Emacs 29.


The code fixing the limitations and bugs of purecopy (at least the ones
triggered while dumping a large variety of loaded libraries) has already
been implemented for 28.1 on my employer's systems.  If they are willing to
donate it (less than 100 lines of C), I'll post a patch.  Even if it won't
be incorporated in the Emacs distribution, Linux vendors who are
conservative in the version of Emacs they package may choose to use it in
their builds.  Aside from supporting bool vectors and strings with text
properties in pure space, it fixes a couple of fatal bugs that can be
triggered while dumping - one segfault and one runaway allocation.

Lynn

[-- Attachment #2: Type: text/html, Size: 1853 bytes --]

      reply	other threads:[~2022-08-07 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 12:15 bug#57035: Support for site-load.el in native-compile dumping Lynn Winebarger
2022-08-07 12:55 ` Lars Ingebrigtsen
2022-08-07 13:16   ` Lynn Winebarger [this message]

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=bBdhugCWp_j+-bC6fjoHQnkjzP3j0n6JeQ9U9hOTOmCsQ@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=57035@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).