From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: eller.helmut@gmail.com, acorallo@gnu.org, emacs-devel@gnu.org
Subject: Re: MPS codegen
Date: Fri, 14 Jun 2024 17:33:25 +0300 [thread overview]
Message-ID: <865xuby4p6.fsf@gnu.org> (raw)
In-Reply-To: <m2ikybboxc.fsf@pro2.fritz.box> (message from Gerd Möllmann on Fri, 14 Jun 2024 16:05:03 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: eller.helmut@gmail.com, acorallo@gnu.org, emacs-devel@gnu.org
> Date: Fri, 14 Jun 2024 16:05:03 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> What I was trying to convey is kust that in this case mirror_fwd is used.
> >
> > Is or should be?
>
> Is.
>
> > I see mirror_fwd used only in igc.c, and it's a static function there.
> >
> > I guess what I'm saying is that I don't understand what you suggest to
> > do or check to try to fix these segfaults.
>
> One big difference to before is that the object graph in the loaded dump
> is copied top MPS (see igc_on_pdump_loaded).
>
> This proceeds in steps.
>
> 1. iterate over objects in the dump and copy them. Record for each
> object in dump what its copy is (igc_mirror::dump_to_mps).
>
> 2. iterate over objects in the copy, and "mirror" references, i.e.
> replace references to the old graph with references in the copy.
> Here, mirror_fwd comes into play, as subroutine of mirror_symbol.
>
> 3. Fix roots in a similar way.
>
> 4. Discard the dump.
>
> I'd probably put a breakpoitn in mirror_fwd and look around if something
> there is not right for IA32, or Windows, don't know.
Thanks. But this kind of journey down the rabbit hole (mirror_fwd
leads to IGC_MIRROR_OBJ, which leads to mirror_lisp_obj, which leads
to look up_copy and a bunch of other functions whose functionality is
not documented anywhere) will have to wait for someone else. Sorry, I
have too much on my plate at this time: need to start the Emacs 30
release cycle.
I can only say that I tried to bisect your changes installed today,
and failed: almost all of the commits between 219f7d5 (the last one
which builds and works) and HEAD don't even compile due to compilation
errors (undeclared variables, missing functions, etc.), and those
which do compile crash when Emacs attempts to byte-compile some Lisp.
My guess is that something very basic in dumping and/or loading from
the pdumper file became broken, but due to the above I cannot pinpoint
the commit which broke it. Sorry.
I'll happily test any change you or Helmut or anyone else suggests.
next prev parent reply other threads:[~2024-06-14 14:33 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 13:39 MPS: Update Gerd Möllmann
2024-06-10 16:17 ` Andrea Corallo
2024-06-10 16:26 ` Gerd Möllmann
2024-06-10 16:44 ` Gerd Möllmann
2024-06-10 20:58 ` Andrea Corallo
2024-06-11 3:12 ` Gerd Möllmann
2024-06-11 20:35 ` Helmut Eller
2024-06-12 4:45 ` Gerd Möllmann
2024-06-12 7:54 ` Eli Zaretskii
2024-06-12 8:00 ` Gerd Möllmann
2024-06-13 9:07 ` MPS codegen (was: MPS: Update) Helmut Eller
2024-06-13 12:33 ` MPS codegen Gerd Möllmann
2024-06-13 17:48 ` Helmut Eller
2024-06-13 18:24 ` Gerd Möllmann
2024-06-13 18:31 ` Gerd Möllmann
2024-06-13 18:38 ` Helmut Eller
2024-06-13 18:54 ` Gerd Möllmann
2024-06-13 19:15 ` Helmut Eller
2024-06-13 19:37 ` Gerd Möllmann
2024-06-14 6:37 ` Eli Zaretskii
2024-06-14 7:30 ` Gerd Möllmann
2024-06-14 7:56 ` Gerd Möllmann
2024-06-14 10:52 ` Eli Zaretskii
2024-06-14 10:46 ` Eli Zaretskii
2024-06-13 23:09 ` Andrea Corallo
2024-06-14 6:08 ` Gerd Möllmann
2024-06-14 7:45 ` Helmut Eller
2024-06-14 7:59 ` Gerd Möllmann
2024-06-14 8:28 ` Gerd Möllmann
2024-06-14 8:51 ` Helmut Eller
2024-06-14 11:32 ` Eli Zaretskii
2024-06-14 12:43 ` Gerd Möllmann
2024-06-14 13:04 ` Eli Zaretskii
2024-06-14 13:17 ` Gerd Möllmann
2024-06-14 13:46 ` Eli Zaretskii
2024-06-14 14:05 ` Gerd Möllmann
2024-06-14 14:33 ` Eli Zaretskii [this message]
2024-06-14 14:46 ` Gerd Möllmann
2024-06-14 16:30 ` Helmut Eller
2024-06-14 18:28 ` Eli Zaretskii
2024-06-14 19:03 ` Eli Zaretskii
2024-06-14 19:26 ` Helmut Eller
2024-06-14 19:50 ` Gerd Möllmann
2024-06-15 6:26 ` Eli Zaretskii
2024-06-15 7:10 ` Gerd Möllmann
2024-06-15 7:34 ` Eli Zaretskii
2024-06-15 8:22 ` Gerd Möllmann
2024-06-15 6:11 ` Eli Zaretskii
2024-06-15 7:25 ` Gerd Möllmann
2024-06-15 7:46 ` Eli Zaretskii
2024-06-15 8:14 ` Gerd Möllmann
2024-06-15 8:38 ` Gerd Möllmann
2024-06-15 8:44 ` Helmut Eller
2024-06-15 8:56 ` Gerd Möllmann
2024-06-15 9:07 ` Helmut Eller
2024-06-15 9:27 ` Gerd Möllmann
2024-06-15 12:33 ` Gerd Möllmann
2024-06-16 6:16 ` Gerd Möllmann
2024-06-16 7:53 ` Eli Zaretskii
2024-06-16 8:19 ` Gerd Möllmann
2024-06-16 8:40 ` Helmut Eller
2024-06-16 8:49 ` 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=865xuby4p6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acorallo@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).