all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Pip Cet <pipcet@protonmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: MPS: nativecomp ABI
Date: Sat, 06 Jul 2024 13:53:43 -0400	[thread overview]
Message-ID: <yp18qyeh0ew.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <hbIh703-JB_42jzsfnA82CqNFu-dtuTdyAGgdxo1BPRrmP5J2kXPv8pCTYA49wHCminPy7sFeaudc758eHpuwj-X5JMHx4HM3NXyCGQVWO0=@protonmail.com> (Pip Cet's message of "Fri, 05 Jul 2024 14:44:16 +0000")

Pip Cet <pipcet@protonmail.com> writes:

> Hello,
>
> I'm working on scratch/igc. One thing I'd like to do is put the IGC header which all objects will require (for now) into these structs:
>
> struct Lisp_Cons
> struct Lisp_Symbol
> struct Lisp_String
> struct Lisp_Float
> union vectorlike_header
>
> IIUC, this means changing the nativecomp ABI hash (which means I'll
> have to rebuild the .eln files, I think) and adjusting any nativecomp
> code which knows about the structure layouts. However, I've only been
> able to find that for Lisp_Cons and struct Lisp_Symbol_With_Pos, which
> declares its header as ptrdiff_t. Are there more, or do the others all
> use C functions for access?
>
> Things appear to work, but I'd rather not miss anything and haven't looked at this code in years.
>
> Thanks!
> Pip

Hello,

I believe the easiest is that you compile a .eln with
native-comp-debug >= 2 and have a look to the generated pseudo C.

Indipendently to the code being compiled, on top you'll see all the
structures defined to libgccjit.

I'll not have access to a machine where I can do it before next week but
this is the easiest way to aswer your question.

  Andrea



  reply	other threads:[~2024-07-06 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 14:44 MPS: nativecomp ABI Pip Cet
2024-07-06 17:53 ` Andrea Corallo [this message]
2024-07-07 19:11   ` Pip Cet
2024-07-08  9:08     ` Andrea Corallo

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=yp18qyeh0ew.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@protonmail.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 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.