From: <tomas@tuxteam.de>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Helmut Eller <eller.helmut@gmail.com>,
gerd.moellmann@gmail.com, emacs-devel@gnu.org
Subject: Re: Question about code generation
Date: Fri, 10 May 2024 19:21:36 +0200 [thread overview]
Message-ID: <Zj5XoGFAgmyQrqrl@tuxteam.de> (raw)
In-Reply-To: <yp1v83lvby4.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Fri, May 10, 2024 at 01:00:51PM -0400, Andrea Corallo wrote:
[...]
> I think in this case libgccjit goes the other way of what would be need
> here. Libgccjit allowed us to develop an Elisp front-end while here the
> frontend we need is already the C one that comes with GCC.
>
> What we want is a GCC plugin, essentially a custom pass that analyses
> say lisp.h and output something (in this case some C code).
>
> Not many people know that should be even possible to write it in python
> thanks to David Malcolm work
> <https://gcc-python-plugin.readthedocs.io/en/latest/>, certanly not
> Elisp :/ but probably quicker than doing it in C.
And then, there is MELT [1], by Basile Starynkevitch, which, AFAIR is
a Lispy GCC plugin.
Cheers
[1] https://gcc.gnu.org/wiki/MiddleEndLispTranslator
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-05-10 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 9:33 Question about code generation Gerd Möllmann
2024-05-10 10:35 ` Eli Zaretskii
2024-05-10 11:38 ` Gerd Möllmann
2024-05-10 12:57 ` Helmut Eller
2024-05-10 12:59 ` Gerd Möllmann
2024-05-10 15:16 ` Eli Zaretskii
2024-05-10 17:00 ` Andrea Corallo
2024-05-10 17:21 ` tomas [this message]
2024-05-10 17:35 ` Andrea Corallo
2024-05-10 17:38 ` Andrea Corallo
2024-05-10 17:38 ` tomas
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=Zj5XoGFAgmyQrqrl@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.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.