public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org,  Andrea Corallo <Andrea.Corallo@arm.com>
Subject: Re: Debug info on macOS
Date: Sat, 11 May 2024 05:39:17 +0200	[thread overview]
Message-ID: <m2seyp10gq.fsf@pro2.fritz.box> (raw)
In-Reply-To: <7fee40c1649f53f2e2270084bfceac51f6ff7a36.camel@redhat.com> (David Malcolm's message of "Fri, 10 May 2024 16:17:09 -0400")

David Malcolm <dmalcolm@redhat.com> writes:

> As I understand it, Emacs is using libgccjit to do ahead-of-time
> compilation, presumably compiling the optimized ELisp code to machine
> code as a shared library.

Correct.

> Is Emacs using gcc_jit_context_compile_to_file with
> GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY, or is it doing something more
> complicated?

Yes. (Sorry, I forgot to CC Andrea; he sent me here :-)).

> If that's what it's doing, you might want to take a look
> at playback::context::compile in gcc/jit-playback.cc (and try stepping
> through it in the debugger).  In particular, the
> playback::compile_to_file::postprocess implementation of the
> playback::context::postprocess vfunc is responsible for taking a .s in
> a tempdir and turning it into the desired output.  Perhaps there's some
> macOS-specific special-casing needed there?
>
> You might also find it useful to look at the overview of how
> libgccjit's internals here:
> https://gcc.gnu.org/onlinedocs/jit/internals/index.html#overview-of-code-structure
>
> Hope this is helpful

Yes it is. Thanks, David!

  parent reply	other threads:[~2024-05-11  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 13:46 Gerd Möllmann
2024-05-10 20:17 ` David Malcolm
2024-05-10 22:11   ` Andrea Corallo
2024-05-11  3:39   ` Gerd Möllmann [this message]
2024-05-31  4:09     ` 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=m2seyp10gq.fsf@pro2.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=Andrea.Corallo@arm.com \
    --cc=dmalcolm@redhat.com \
    --cc=jit@gcc.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.
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).