From: Joshua Saxby <joshua.a.saxby@gmail.com>
To: jit@gcc.gnu.org
Subject: Modifying the jit compiler API?
Date: Sat, 10 Jun 2023 00:04:43 +0100 [thread overview]
Message-ID: <CALPFi8M=q_hNqa-GXaUdiZ8025JF=Qnp=Z9nth8Dx0j8m9xhOA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
Currently the JIT has two functions allowing you to compile a context
either to memory or to file.
But what if you want to compile to both? There doesn't seem to be any way
to do this except by calling both functions separately which I believe will
effectively be two separate compilations...
Presumably, it should be possible to modify this part of the API to compile
to some form of intermediate representation of the work that is common to
both kinds of compilation, and then turn that into code in memory and in
file, respectively.
Anyone got any pointers for me on where in the code would be the best place
for me to modify to dupport this? I did take a look in the implementation
code of JIT sone weeks ago and remember seeing lots of complicated stuff
regarding recordings and replays that looked relevant...
A slighty simpler alteration I am also interested in making is allowing
compile to file to compile to a buffer in memory as well as a file (I
suppose it could be termed "compile to binary"). Maybe I should start with
that...
reply other threads:[~2023-06-09 23:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALPFi8M=q_hNqa-GXaUdiZ8025JF=Qnp=Z9nth8Dx0j8m9xhOA@mail.gmail.com' \
--to=joshua.a.saxby@gmail.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).