unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>, guile-devel@gnu.org
Cc: Atsuro Hoshino <hoshinoatsuro@gmail.com>
Subject: Re: Experimental JIT for Guile (???!)
Date: Wed, 28 Sep 2016 12:11:15 +0800	[thread overview]
Message-ID: <1475035875.18187.50.camel@gmail.com> (raw)
In-Reply-To: <87bmz91c9t.fsf@dustycloud.org>

Well, there's interesting story behind it.
Few days ago this new JIT backend named Nash was introduced in ICFP2016 (scheme
workshop), I and Ludo are lecturers too. When I first saw the topic, I looked
back to Ludo and thought "oh you guys are making a new weapon secretly huh?"
I thought this work must be encouraged and helped by Ludo or Wingo or Mark, but
finally I realized that I was wrong, the author Atsuro Hoshino was hacking JIT
backend for Guile all by himself. Ludo got surprised too.
I have to say, lone hero pattern is not recommended for a community project, but
anyway he did it bravely and the result seems good according to the paper.
After the meeting, I and Ludo tried to convince him to get involved into our
community to get more help and feedback. 

I CC him here, and it depends on him whether/when to introduce more.

I think this project is just amazing, really! Thank you Hoshino! ;-)

Best regards.

On Tue, 2016-09-27 at 12:30 -0500, Christopher Allan Webber wrote:
> Earlier today, David Thompson pointed to this paper in #guix on
> freenode:
> 
>   https://github.com/8c6794b6/guile-tjit-documentation/raw/master/nash.pdf
> 
> And here seems to be the source:
> 
>   https://github.com/8c6794b6/guile-tjit
> 
> I'm not informed enough to judge this myself, but this seems like a
> reasonable start-of-implementation of the ideas expressed here:
> 
>   http://wingolog.org/archives/2015/11/03/two-paths-one-peak-a-view-from-below
> -on-high-performance-language-implementations
> 
> It mentions hot loops and compiling to native code... that's about as
> much as I can tell myself about it being on track.  But it seems pretty
> cool, especially for something shooting onto the radar seemingly out of
> nowhere!
> 
> Anyone more informed have thoughts? :)
>  - Chris
> 




  reply	other threads:[~2016-09-28  4:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 17:30 Experimental JIT for Guile (???!) Christopher Allan Webber
2016-09-28  4:11 ` Nala Ginrut [this message]
2016-09-28  7:45   ` Christopher Allan Webber
2016-09-28 12:17     ` Amirouche Boubekki
2016-10-03 20:38   ` Ludovic Courtès
2016-10-03 22:21     ` Lluís Vilanova
2016-10-04  7:58       ` Ludovic Courtès
2016-10-04  9:57         ` Lluís Vilanova
2016-10-04 12:52           ` Ludovic Courtès

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=1475035875.18187.50.camel@gmail.com \
    --to=nalaginrut@gmail.com \
    --cc=cwebber@dustycloud.org \
    --cc=guile-devel@gnu.org \
    --cc=hoshinoatsuro@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).