unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@protonmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: MPS: nativecomp ABI
Date: Sun, 07 Jul 2024 19:11:55 +0000	[thread overview]
Message-ID: <z8hT_5yKDWCVKNq9oCamqKyGYQV5UMSgBeN_RTXMbtJDHC-oAPcqedfEdJxjG3K738FuURwcxCXRMMMV0SXjPR0sfSIad2fN9qS6lkajdho=@protonmail.com> (raw)
In-Reply-To: <yp18qyeh0ew.fsf@fencepost.gnu.org>

On Saturday, July 6th, 2024 at 17:53, Andrea Corallo <acorallo@gnu.org> wrote:
> Pip Cet pipcet@protonmail.com writes:
> > 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

> 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.

Thanks for the advice. That worked for me, though I must confess I was looking in the wrong place for the pseudo-C code.

Pip



  reply	other threads:[~2024-07-07 19:11 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
2024-07-07 19:11   ` Pip Cet [this message]
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

  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='z8hT_5yKDWCVKNq9oCamqKyGYQV5UMSgBeN_RTXMbtJDHC-oAPcqedfEdJxjG3K738FuURwcxCXRMMMV0SXjPR0sfSIad2fN9qS6lkajdho=@protonmail.com' \
    --to=pipcet@protonmail.com \
    --cc=acorallo@gnu.org \
    --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).