From: Samuel Crow <samueldcrow@gmail.com>
To: jit@gcc.gnu.org
Subject: Proposed showcase piece for libGCCJIT: WebAssembly frontend
Date: Mon, 9 Jan 2023 03:45:42 +0000 [thread overview]
Message-ID: <CAOP8J0YrDfxQ3-tV4J-htpActhADSMm1=o7-H8F1kUbEn7LpjQ@mail.gmail.com> (raw)
Greetings!
As a contributer to the W2C2 project on GitHub (
https://github.com/turbolent/w2c2 ), I was wondering if a static
compiler that tied in to the LibGCCJIT frontend would be a good idea
for a showcase piece. If yes, I have an idea for a compilation
algorithm that should make the compilation quite parallelizable.
Currently, the build of W2C2 can output multiple C files from one
WebAssembly module using the WASI standard as a linkage target so that
the functions can parallel build. I have a plan that can take that a
step farther but I'm not sure if the JIT frontend is best or just a
custom GCC frontend.
I've just joined the mailing list so I'll just leave this as a teaser
for now. If interested I'll spell it out in greater detail later.
One thing that prompted me to ask is that several of the showcase
pieces on the LibGCCJIT webpage that tried it have since moved on to
other JIT compilers or are no longer available. I like the idea of
having GCC in a shared object though, even if for no other reason than
to be able to run it as reentrant code.
I'm typing this message from the Beta 4 of Haiku Release 1 and just
love that GCC is used on so many platfroms including this one.
Yours truly,
Samuel D. Crow
reply other threads:[~2023-01-09 3:45 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='CAOP8J0YrDfxQ3-tV4J-htpActhADSMm1=o7-H8F1kUbEn7LpjQ@mail.gmail.com' \
--to=samueldcrow@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).