unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Andy Wingo <wingo@igalia.com>, Mark H Weaver <mhw@netris.org>,
	Atsuro Hoshino <hoshinoatsuro@gmail.com>,
	guile-devel@gnu.org
Subject: Re: Experimental JIT for Guile (???!)
Date: Tue, 04 Oct 2016 09:58:50 +0200	[thread overview]
Message-ID: <87mvikfsud.fsf@gnu.org> (raw)
In-Reply-To: <87d1jh13ca.fsf@fimbulvetr.bsc.es> ("Lluís Vilanova"'s message of "Tue, 04 Oct 2016 00:21:09 +0200")

Hello!

Lluís Vilanova <vilanova@ac.upc.edu> skribis:

> Still, this mail made me think if optimizations based on "tracing" (or any kind
> of runtime-based profiling) could be nested. Then you could start by applying
> the existing compiler optimizations, later generate a procedure/trace version
> dispatcher with unboxed operations (you can add new versions as they become
> hot), and only at the end generate native code.

I’m not sure what you mean by “nested”.  What tracing JITs and Nash do
is collect execution traces, and trigger native code compilation once a
given segment of code (a loop body) has been executed a number of times.
The generated code is specialized according to that trace.

Ludo’.



  reply	other threads:[~2016-10-04  7:58 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
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 [this message]
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=87mvikfsud.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=hoshinoatsuro@gmail.com \
    --cc=mhw@netris.org \
    --cc=nalaginrut@gmail.com \
    --cc=wingo@igalia.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).