From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: MPS: Loaded pdump
Date: Thu, 09 May 2024 20:24:12 +0200 [thread overview]
Message-ID: <m2bk5ealo3.fsf@pro2.fritz.box> (raw)
In-Reply-To: <87seyrni6f.fsf@gmail.com> (Helmut Eller's message of "Thu, 09 May 2024 17:01:12 +0200")
Helmut Eller <eller.helmut@gmail.com> writes:
> On Thu, May 09 2024, Gerd Möllmann wrote:
>
>> Helmut Eller <eller.helmut@gmail.com> writes:
>>
>>> On Thu, May 09 2024, Gerd Möllmann wrote:
>>>
>>>> - The root is unstructured. We can't scan exactly, and so can't do
>>>> anything special for pointers to non-MPS memory that Lisp objects
>>>> have. This leads to some horrible workarounds.
>>>
>>> The pdumper could put the different types (cons, symbol, string,
>>> vectorlike) in different sections. Then we could probably scan it
>>> exactly.
>>
>> Either that, or we could dump the igc_header with the objects. Don't
>> know how difficult that would be. My gut tells me introducing more
>> sections than the 3 we have could be more work.
>
> Had forgotten about that; with the additional advantage that the
> existing scan code would work right away.
But this looks also interesting
struct dump_header
{
...
/* "Relocation" table we abuse to hold information about the
location and type of each lisp object in the dump. We need for
pdumper_object_type and ultimately for conservative GC
correctness. */
struct dump_table_locator object_starts;
I think I'll read the pdumper code a bit more in the next days.
next prev parent reply other threads:[~2024-05-09 18:24 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 10:52 MPS: Loaded pdump Gerd Möllmann
2024-05-09 11:00 ` Eli Zaretskii
2024-05-09 11:20 ` Gerd Möllmann
2024-05-09 12:28 ` Helmut Eller
2024-05-09 13:37 ` Gerd Möllmann
2024-05-09 16:10 ` Helmut Eller
2024-05-09 16:43 ` Gerd Möllmann
2024-05-09 17:57 ` Helmut Eller
2024-05-09 18:10 ` Gerd Möllmann
2024-05-09 13:38 ` Helmut Eller
2024-05-09 14:18 ` Gerd Möllmann
2024-05-09 15:01 ` Helmut Eller
2024-05-09 15:07 ` Gerd Möllmann
2024-05-10 7:59 ` Gerd Möllmann
2024-05-10 8:09 ` Helmut Eller
2024-05-10 8:35 ` Gerd Möllmann
2024-05-10 8:51 ` Helmut Eller
2024-05-10 8:54 ` Gerd Möllmann
2024-05-10 10:25 ` Eli Zaretskii
2024-05-10 11:31 ` Gerd Möllmann
2024-05-10 12:52 ` Gerd Möllmann
2024-05-10 13:37 ` Helmut Eller
2024-05-10 13:59 ` Gerd Möllmann
2024-05-10 14:31 ` Helmut Eller
2024-05-10 14:36 ` Gerd Möllmann
2024-05-13 9:11 ` Gerd Möllmann
2024-05-14 8:23 ` Gerd Möllmann
2024-05-14 14:22 ` Helmut Eller
2024-05-14 15:46 ` Gerd Möllmann
2024-05-14 17:49 ` Eli Zaretskii
2024-05-14 18:10 ` Gerd Möllmann
2024-05-16 4:25 ` Gerd Möllmann
2024-05-16 8:36 ` Helmut Eller
2024-05-16 8:46 ` Gerd Möllmann
2024-05-16 9:01 ` Gerd Möllmann
2024-05-16 9:31 ` Helmut Eller
2024-05-16 9:42 ` Gerd Möllmann
2024-05-16 9:54 ` Gerd Möllmann
2024-05-16 12:43 ` Helmut Eller
2024-05-16 12:47 ` Gerd Möllmann
2024-05-16 12:08 ` Eli Zaretskii
2024-05-16 12:27 ` Gerd Möllmann
2024-05-16 12:07 ` Eli Zaretskii
2024-05-16 12:21 ` Gerd Möllmann
2024-05-16 12:27 ` Eli Zaretskii
2024-05-16 12:43 ` Gerd Möllmann
2024-05-16 14:09 ` Helmut Eller
2024-05-16 14:24 ` Gerd Möllmann
2024-05-16 15:48 ` Eli Zaretskii
2024-05-16 16:56 ` Andrea Corallo
2024-05-16 17:27 ` Gerd Möllmann
2024-05-16 17:50 ` Andrea Corallo
2024-05-16 20:03 ` Helmut Eller
2024-05-17 4:04 ` Gerd Möllmann
2024-05-17 6:09 ` Eli Zaretskii
2024-05-18 18:55 ` Helmut Eller
2024-05-18 20:16 ` Andrea Corallo
2024-05-19 5:27 ` Eli Zaretskii
2024-05-19 3:48 ` Gerd Möllmann
2024-05-19 6:39 ` Eli Zaretskii
2024-05-09 18:24 ` Gerd Möllmann [this message]
2024-05-09 18:35 ` 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
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=m2bk5ealo3.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--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).