From: Andy Wingo <wingo@pobox.com>
To: Sjoerd van Leent <svanleent@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: on native compilation
Date: Tue, 17 Sep 2013 19:07:41 +0200 [thread overview]
Message-ID: <87hadjv0ki.fsf@pobox.com> (raw)
In-Reply-To: <CACqzbVga-dY4v447OsPsR0hiZB+t+ZqeezGjSwyNwio97uSEHA@mail.gmail.com> (Sjoerd van Leent's message of "Sun, 8 Sep 2013 20:19:22 +0200")
Hi,
On Sun 08 Sep 2013 20:19, Sjoerd van Leent <svanleent@gmail.com> writes:
> Reading the written thoughts below, what was the actual reason no to use
> GNU Lightning? Has that too many complexities or incompatibilities to be
> used for Scheme and other functional languages opposed to it's native
> GNU Smalltalk?
>
> I ask this since recently GNU Lightning 2.0 has seen the light, and I
> just wonder if it would be wise to reinvestigate.
It makes sense to investigate, yes. However the issue is more one of
getting getting the right abstractions in Guile, and it's not clear that
Lightning provides them. Lightning is for JIT compilation, and we want
to do AOT first. I think it makes sense to get native code for one
architecture, see how that interacts with our needs for debugging, then
start to think if an existing project's code generation abstractions
suit our needs.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-09-17 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 11:12 on native compilation Andy Wingo
2013-09-02 5:07 ` Nala Ginrut
2013-09-08 18:19 ` Sjoerd van Leent
2013-09-17 17:07 ` Andy Wingo [this message]
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=87hadjv0ki.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=svanleent@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.
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).