From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, Helmut Eller <eller.helmut@gmail.com>
Subject: Re: MPS: native comp
Date: Thu, 09 May 2024 11:12:34 +0200 [thread overview]
Message-ID: <m2wmo3bb7h.fsf@pro2.fritz.box> (raw)
In-Reply-To: <m25xvncxzb.fsf@pro2.fritz.box> ("Gerd Möllmann"'s message of "Thu, 09 May 2024 08:15:20 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
>> Andrea Corallo <acorallo@gnu.org> writes:
>>
>>>> Current_thread is staticpro'd, so in Emacs we'll fix that if a
>>>> thread_sate moves in memory. But what does/could GCC assume about this,
>>>> or maybe comp?
>>>
>>> I think we'll have to update "struct comp_thread_state * *
>>> current_thread_reloc" as well if 'current_thread' moves.
>>
>> Thanks.
>>
>> BTW, is there a way to let libgccjit keep to .o file together with the
>> .c file?
>>
>> I'm asking because the .elns don't have debug info on macOS (for a
>> long-winded reason that made macOS handle DWARF differently from the
>> rest). If I had a .o with debug info, I could maybe generate .dSYM
>> files.
>
> Good news! I think I know what's going on, 100% - epsilon.
>
> The error occurs in an Emacs that has a pdump loaded. (I submitted a bug
> concerning the build process. The workaround for this made it much
> easier for me to recognize what's going on.)
>
> The loaded dump contains, among other things, native compilation unit
> objects. These objects contain pointers into the loaded .eln for things
> that we need to trace. For CUs that are in MPS memory, this is done by
> fix_comp_unit and all it good. For CUs in the dump this is not done,
> simply because they are not in MPS memory but in the hot segment of the
> loaded dump. Result is that references in these .eln are not fixed, and
> so on.
>
> In the end, it's always the same problem with the dump. The dump is not
> in MPS, MPS knows only traces as an ambig root.
>
> I guess we should do something about this. Maybe we could try Helmut's
> idea of copying the objects to MPS.
>
> Meanwhile, I'll try to come up with a workaround.
Bad news! I added a workaround but it's not the fix.
At least not completely. The build with native compilation still fails,
at a different point, but with the same symptom that we hit an unfixed
reference. This time Ffuncall is called from a native-compiled
bytecomp--check-eq-args with a symbol pointing to a tombstone.
So the original question how to get debug info for .elns (maybe by
keeping .o files, as I mentioned) is still important.
I'll transfer what I have later to scratch/igc.
next prev parent reply other threads:[~2024-05-09 9:12 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 5:35 MPS: native comp Gerd Möllmann
2024-04-29 7:29 ` Andrea Corallo
2024-04-29 8:02 ` Gerd Möllmann
2024-04-29 7:52 ` Eli Zaretskii
2024-04-29 8:12 ` Gerd Möllmann
2024-04-29 8:31 ` Gerd Möllmann
2024-04-29 8:40 ` Gerd Möllmann
2024-04-29 8:59 ` Andrea Corallo
2024-04-29 9:09 ` Gerd Möllmann
2024-04-29 9:16 ` Gerd Möllmann
2024-04-29 9:24 ` Andrea Corallo
2024-04-29 9:36 ` Gerd Möllmann
2024-04-29 9:45 ` Andrea Corallo
2024-04-29 9:53 ` Gerd Möllmann
2024-04-29 10:08 ` Andrea Corallo
2024-04-29 10:29 ` Gerd Möllmann
2024-04-29 11:03 ` Andrea Corallo
2024-04-29 11:15 ` Gerd Möllmann
2024-04-30 4:39 ` Gerd Möllmann
2024-04-30 4:58 ` Gerd Möllmann
2024-04-30 5:30 ` Gerd Möllmann
2024-04-30 7:40 ` Andrea Corallo
2024-04-30 8:08 ` Gerd Möllmann
2024-04-30 8:34 ` Gerd Möllmann
2024-04-30 8:57 ` Andrea Corallo
2024-04-30 8:54 ` Andrea Corallo
2024-04-30 9:05 ` Andrea Corallo
2024-04-30 9:18 ` Gerd Möllmann
2024-04-30 9:40 ` Andrea Corallo
2024-04-30 10:27 ` Gerd Möllmann
2024-04-30 10:52 ` Andrea Corallo
2024-04-30 11:54 ` Gerd Möllmann
2024-04-30 12:44 ` Eli Zaretskii
2024-04-30 13:05 ` Andrea Corallo
2024-04-30 13:11 ` Gerd Möllmann
2024-04-30 13:26 ` MPS compilation (was Re: MPS: native comp) Andrea Corallo
2024-04-30 13:35 ` Gerd Möllmann
2024-04-30 14:18 ` Andrea Corallo
2024-04-30 13:26 ` MPS: native comp Eli Zaretskii
2024-04-30 13:45 ` Visuwesh
2024-04-30 14:31 ` Helmut Eller
2024-04-30 12:59 ` Andrea Corallo
2024-04-30 13:06 ` Gerd Möllmann
2024-04-30 14:29 ` Peter Hull
2024-04-30 14:51 ` Gerd Möllmann
2024-04-30 14:02 ` Gerd Möllmann
2024-04-30 17:35 ` Gerd Möllmann
2024-05-01 5:05 ` Gerd Möllmann
2024-05-02 6:39 ` Gerd Möllmann
2024-05-02 8:56 ` Gerd Möllmann
2024-05-02 14:08 ` Gerd Möllmann
2024-05-02 15:04 ` Eli Zaretskii
2024-05-02 15:56 ` Gerd Möllmann
2024-05-02 16:46 ` Eli Zaretskii
2024-05-02 15:14 ` Helmut Eller
2024-05-02 15:58 ` Gerd Möllmann
2024-05-02 16:37 ` Helmut Eller
2024-05-02 19:49 ` Gerd Möllmann
2024-05-03 5:56 ` Helmut Eller
2024-05-03 6:29 ` Gerd Möllmann
2024-05-03 13:38 ` Andrea Corallo
2024-05-03 13:52 ` Helmut Eller
2024-05-03 16:12 ` Andrea Corallo
2024-05-02 10:29 ` Andrea Corallo
2024-05-02 10:51 ` Gerd Möllmann
2024-05-02 10:24 ` Andrea Corallo
2024-05-02 10:49 ` Gerd Möllmann
2024-05-02 21:04 ` Andrea Corallo
2024-05-03 5:35 ` Gerd Möllmann
2024-05-03 13:35 ` Andrea Corallo
2024-05-03 14:19 ` Gerd Möllmann
2024-05-07 8:40 ` Gerd Möllmann
2024-05-07 10:00 ` Andrea Corallo
2024-05-07 12:29 ` Gerd Möllmann
2024-05-08 8:47 ` Gerd Möllmann
2024-05-08 9:12 ` Gerd Möllmann
2024-05-08 15:39 ` Andrea Corallo
2024-05-08 16:11 ` Gerd Möllmann
2024-05-09 6:15 ` Gerd Möllmann
2024-05-09 9:12 ` Gerd Möllmann [this message]
2024-05-10 6:37 ` Andrea Corallo
2024-05-10 6:41 ` Gerd Möllmann
2024-04-30 7:36 ` Andrea Corallo
2024-04-30 7:56 ` Gerd Möllmann
-- strict thread matches above, loose matches on Subject: below --
2024-06-27 14:25 Gerd Möllmann
2024-06-27 14:34 ` Andrea Corallo
2024-06-27 14:36 ` Gerd Möllmann
2024-06-27 15:05 ` Andrea Corallo
2024-06-27 16:39 ` Gerd Möllmann
2024-06-27 16:53 ` Gerd Möllmann
2024-06-27 19:01 ` Andrea Corallo
2024-06-27 19:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wmo3bb7h.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=acorallo@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.