From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Andy Tai" <atai@atai.org>, guile-devel@gnu.org
Subject: Re: guile and libgccjit
Date: Sun, 10 Oct 2021 09:57:13 +0200 [thread overview]
Message-ID: <76173fd8-3d24-4754-bef1-e68c70679b66@www.fastmail.com> (raw)
In-Reply-To: <CAJsg1E8xk6EfqG+EiUo=5dtcRwwqfJxtYEiywSR_LhX+aDi-2w@mail.gmail.com>
The the current JIT is, in my understanding, more or less a stepping stone towards native compilation. The current JIT is very small and lightweight, without any tracing, meaning things like register allocation is flexible going forward.
I am not a maintainer, nor heavily involved, but I believe libgccjit would be a step sideways considering the above.
Best regards
Linus Björnstam
On Sun, 10 Oct 2021, at 01:06, Andy Tai wrote:
> can guile make use of libgccjit?
>
> would be an interesting optional addition to guile
next prev parent reply other threads:[~2021-10-10 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 23:06 guile and libgccjit Andy Tai
2021-10-10 7:57 ` Linus Björnstam [this message]
2021-10-10 8:49 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76173fd8-3d24-4754-bef1-e68c70679b66@www.fastmail.com \
--to=linus.bjornstam@veryfast.biz \
--cc=atai@atai.org \
--cc=guile-devel@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).