From: Daurnimator <quae@daurnimator.com>
To: David Malcolm <dmalcolm@redhat.com>, jit@gcc.gnu.org
Subject: libgccjit questions
Date: Wed, 9 Sep 2020 12:50:42 +1000 [thread overview]
Message-ID: <CAEnbY+cxMW3JjE7Av-sMQS8wLGOPQdcvFrtj3etXkXYdr0+2sw@mail.gmail.com> (raw)
Hi,
I'm looking into using libgccjit as an ahead-of-time compiler to write
a backend for zig (https://ziglang.org/)
I've got a few questions I hope you can answer:
What became of cross-compilation? I saw it mentioned as a possible
roadmap item in
https://gcc.gnu.org/legacy-ml/jit/2015-q3/msg00086.html)
How can I support inline assembly?
Would it be reasonable to add an API that allows extracting sections
without writing out to a file and reading it back in?
Alteratively, would it be possible to get a pointer and length to e.g.
an ELF in memory?
Should distros be packaging libgccjit?
I noticed that e.g. ArchLinux is not. Possibly because it is
documented as "experimental"; possibly because it requires building
gcc with --enable-host-shared ?
What is the license situation with libgccjit; is it GPL? LGPL? what
does this mean for code that uses libgccjit?
Thanks,
Daurnimator
next reply other threads:[~2020-09-09 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 2:50 Daurnimator [this message]
2020-09-09 8:18 ` Andrea Corallo
2020-09-10 22:50 ` David Malcolm
2020-09-11 2:42 ` Daurnimator
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=CAEnbY+cxMW3JjE7Av-sMQS8wLGOPQdcvFrtj3etXkXYdr0+2sw@mail.gmail.com \
--to=quae@daurnimator.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).