unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: Guile User <guile-user@gnu.org>,
	Atsuro Hoshino <hoshinoatsuro@gmail.com>,
	guile-devel <guile-devel@gnu.org>
Subject: Re: The status of JIT compiler of Guile
Date: Tue, 07 Mar 2017 14:23:21 +0100	[thread overview]
Message-ID: <87wpc1dxva.fsf@gnu.org> (raw)
In-Reply-To: <87efygaxkw.fsf@pobox.com> (Andy Wingo's message of "Thu, 02 Mar 2017 09:31:59 +0100")

Howdy!

Andy Wingo <wingo@pobox.com> skribis:

> And hello Atsuro!  I don't think I have had the chance of expressing to
> you how impressive your work is.  Awesome stuff!!!

+1!

> What do you all think is the way forward for this work?  Is it something
> that you see being integrated eventually into Guile git?  Is it a
> project that should be maintained separately?  If the latter, what
> interfaces do you need from Guile?

My understanding is that TJIT/Nash essentially needs a special VM engine
with additional hooks for its tracing:

  https://lists.gnu.org/archive/html/guile-devel/2016-10/msg00001.html

If we make this engine available in Guile proper, then I think Nash
could flourish outside of Guile and yet be usable by anyone running
vanilla Guile.

I haven’t checked if the actual implementation details completely match
this idealized view, but I hope they do.  :-)

WDYT?

Thanks,
Ludo’.



  reply	other threads:[~2017-03-07 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  7:49 The status of JIT compiler of Guile (was: Guile benchmark) Nala Ginrut
2017-03-02  8:31 ` The status of JIT compiler of Guile Andy Wingo
2017-03-07 13:23   ` Ludovic Courtès [this message]
2017-03-09  6:59   ` Nala Ginrut
2017-03-09 14:27     ` Andy Wingo
2017-03-10  6:19       ` Nala Ginrut
2017-03-10  8:14         ` Andy Wingo
2017-03-02  9:10 ` The status of JIT compiler of Guile (was: Guile benchmark) Chaos Eternal
2017-03-06 11:19   ` Nala Ginrut
2017-03-14  2:35     ` Nala Ginrut
2017-03-14  2:37       ` Nala Ginrut

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=87wpc1dxva.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=hoshinoatsuro@gmail.com \
    --cc=wingo@pobox.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).