From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
dancol@dancol.org, eller.helmut@gmail.com, emacs-devel@gnu.org
Subject: Re: MPS: Problem with dynamic modules
Date: Tue, 21 May 2024 10:25:10 +0200 [thread overview]
Message-ID: <m2r0dvbmhl.fsf@pro2.fritz.box> (raw)
In-Reply-To: <yp18r0338ej.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Tue, 21 May 2024 03:56:36 -0400")
Andrea Corallo <acorallo@gnu.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>>> Cc: dancol@dancol.org, eller.helmut@gmail.com, emacs-devel@gnu.org
>>> Date: Mon, 20 May 2024 15:23:21 +0200
>>>
>>> Isn't there something easier? Can emacs_value_tag be changed to
>>> something containing s struct Lisp_X *, for example? I think that's what
>>> native comp does, at least judging from the C that it generates.
>>
>> Andrea, can you help us here, please?
>
> Sure,
>
> Gerd I'm not sure what you refer to, in native code we don't do any
> wrapping different form what we do in C (AFAIR), maybe you've a piece of
> generated code you are looking at as example?
This is not about wrapping.
emacs_value_tag is a struct containing a Lisp_Object member. The
question is if it could use struct Lisp_X * instead of Lisp_Object for
the member.
next prev parent reply other threads:[~2024-05-21 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 13:01 MPS: Problem with dynamic modules Gerd Möllmann
2024-05-19 13:21 ` Eli Zaretskii
2024-05-19 13:58 ` Gerd Möllmann
2024-05-19 15:37 ` Eli Zaretskii
2024-05-19 16:17 ` Gerd Möllmann
2024-05-19 16:28 ` Eli Zaretskii
2024-05-19 16:47 ` Gerd Möllmann
2024-05-20 5:35 ` Gerd Möllmann
2024-05-20 11:50 ` Eli Zaretskii
2024-05-20 12:07 ` Gerd Möllmann
2024-05-20 13:06 ` Eli Zaretskii
2024-05-20 13:23 ` Gerd Möllmann
2024-05-20 13:50 ` Eli Zaretskii
2024-05-21 7:56 ` Andrea Corallo
2024-05-21 8:25 ` Gerd Möllmann [this message]
2024-05-21 10:26 ` Andrea Corallo
2024-05-21 11: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r0dvbmhl.fsf@pro2.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=acorallo@gnu.org \
--cc=dancol@dancol.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.