From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Noah Lavine Newsgroups: gmane.lisp.guile.devel Subject: Re: wip-rtl, solstice edition Date: Mon, 25 Jun 2012 18:01:18 -0400 Message-ID: References: <87sjdnz2gt.fsf@pobox.com> <87k3yvxgfk.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1340661689 2383 80.91.229.3 (25 Jun 2012 22:01:29 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 25 Jun 2012 22:01:29 +0000 (UTC) Cc: guile-devel@gnu.org To: =?ISO-8859-1?Q?Ludovic_Court=E8s?= Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Jun 26 00:01:29 2012 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SjHLa-0000UO-Ny for guile-devel@m.gmane.org; Tue, 26 Jun 2012 00:01:26 +0200 Original-Received: from localhost ([::1]:41326 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjHLa-0008VT-KZ for guile-devel@m.gmane.org; Mon, 25 Jun 2012 18:01:26 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:41402) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjHLX-0008V8-HB for guile-devel@gnu.org; Mon, 25 Jun 2012 18:01:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SjHLV-0000V4-Qx for guile-devel@gnu.org; Mon, 25 Jun 2012 18:01:23 -0400 Original-Received: from mail-ob0-f169.google.com ([209.85.214.169]:65401) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjHLV-0000UC-KC; Mon, 25 Jun 2012 18:01:21 -0400 Original-Received: by obhx4 with SMTP id x4so9160669obh.0 for ; Mon, 25 Jun 2012 15:01:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DB+vXSo6a7XcXFB7//WuUGiCoqC66r6gF4xtOpXYL7w=; b=Ik1zD7lcP/oYy318xiELr8TqclSwvgITWpbiuh1yPqmgZDLEffOBy4ZAvwbRwNd1mL ofqoPsiP2//S9DAoxE0t+mCJecyndHQBUye2Nhz1+7DJrVrl5b+8MGnrraOr/kjUvEzI vmdBdLzjjrnfs3sUlL1Hd1fwPrr2bXZ58wtnFkgPBU7YmyqL4WKU7He1d3Z1i6WuhcMN YyW1RlB5HE+59dGN/l9JbyUlMjK/0xIHc3A4NSLAHipOW/Mpu90819lP8jAREwPfjoMg MQrwfmD3FbqO4u9XaAD/J9/OVZvuZkmAMqNDxirVo1oALDwNzct40oD7C6bQ81hrkfZn aQvw== Original-Received: by 10.60.8.35 with SMTP id o3mr13742287oea.45.1340661678200; Mon, 25 Jun 2012 15:01:18 -0700 (PDT) Original-Received: by 10.76.82.68 with HTTP; Mon, 25 Jun 2012 15:01:18 -0700 (PDT) In-Reply-To: <87k3yvxgfk.fsf@gnu.org> X-Google-Sender-Auth: UpNQ91hsQqbwBd2FGVkipEvB9EA X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.214.169 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:14667 Archived-At: Hello, > Seriously though, that seems like a good plan. =A0I wonder what Noah=92s > attempts at JITing the 2.0 bytecode would have achieved, though, if we > think of both JIT and the new VM as an =93interim solution=94 before AOT > native compilation. I can't remember the last email I sent about that, but I think I might have dropped the ball here, so let me say what the current status of the project was. The JIT compiler worked fine. You could JIT-compile a function and have Guile automatically run the JITted code. The real problem was writing the JIT compiler - the one I had only supported four instructions, because I just wanted to prove I could integrate it with the rest of Guile. I sent another email recently about different ways to make the JITter understand all of the bytecode, but at the time, I thought I would have to parse the C definition of the VM and generate the JITter from that in order for it to be merged into Guile. I never got over that hurdle. If we are willing to generate both the VM and the JITter from another source, it's possible that I could revive my old JIT branch. However, I'm still not sure if that's the best way there. Having the assembler written in Scheme gives you an easier path towards all-Scheme native compilation, which you'd probably want for an AOT compiler. Noah