unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: GLIL->C compilation
Date: Sat, 20 Nov 2010 00:56:19 +0100	[thread overview]
Message-ID: <87mxp4vpek.fsf@gnu.org> (raw)
In-Reply-To: 201011200020.04169.stefan.itampe@gmail.com

Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:

> On Saturday, November 20, 2010 12:11:16 am Ludovic Courtès wrote:
>> Hi,
>> 
>> Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
>> > #include "cfkn.h"
>> > #define LOCAL_REF(i)     fp[i]
>> > #define LOCAL_SET(i,v)   fp[i] = (v)
>> > void cfkn3676(SCM *fp, SCM **spp)
>> > {
>> > 
>> >  /* setup of environment */
>> >  SCM *objects, *free, program, *sp, sss[100];
>> >  sp = sss;
>> >  program = fp[-1];
>> >  objects = SCM_I_VECTOR_WELTS (SCM_PROGRAM_OBJTABLE (program));
>> >  free    = SCM_PROGRAM_FREE_VARIABLES(program);
>> >  /* compiled section */
>> > 
>> >  LCASE3666:
>> > goto L3668;
>> > LCASE3665:
>> > sp++; *sp = LOCAL_REF(1);
>> > sp++; *sp = SCM_I_MAKINUM(0);
>> > sp-=2; if(!scm_is_eq(sp[1],sp[2])) goto L3669;
>> > sp++; *sp = LOCAL_REF(2);
>> 
>> [...]
>> 
>> Comparing this to the VM’s bytecode interpreter should show the overhead
>> incurred by instruction dispatch.
>> 
>> Did you try to measure this?  That’d be interesting.
>> 
>> Thanks,
>> Ludo’.
>
> Yes on one of my machine one loop takes about 6ns for the compiled one and 
> about 50ns for the bytcode, say a factor of 7-10 for simple tasks, but 
> remember
> this is for rather trivial work.

Woow, I didn’t expect so much.

Ludo’.




  reply	other threads:[~2010-11-19 23:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 20:23 The progress of hacking guile and prolog Stefan Israelsson Tampe
2010-11-03 23:43 ` Ludovic Courtès
2010-11-04  2:40   ` Noah Lavine
2010-11-10 17:55     ` Stefan Israelsson Tampe
2010-11-11 19:10       ` Noah Lavine
2010-11-11 16:26     ` Ludovic Courtès
2010-11-11 19:13       ` Noah Lavine
2010-11-11 19:15       ` Noah Lavine
2010-11-15 23:10     ` Typechecking I Stefan Israelsson Tampe
2010-11-20 11:46       ` Andy Wingo
2010-11-20 11:25     ` The progress of hacking guile and prolog Andy Wingo
2010-11-24  1:54       ` Noah Lavine
2010-11-24 16:45         ` Stefan Israelsson Tampe
2010-11-24 18:00         ` piper schemigan Stefan Israelsson Tampe
2010-11-24 20:18           ` Andreas Rottmann
2010-11-25 21:17           ` Ludovic Courtès
2010-11-26 22:18             ` Stefan Israelsson Tampe
2010-11-28 22:30               ` Guile-SCSH Ludovic Courtès
2010-11-28 23:02                 ` Guile-SCSH Stefan Israelsson Tampe
2010-11-28 23:24                   ` Guile-SCSH Jose A. Ortega Ruiz
2010-11-29 18:56                     ` Guile-SCSH Stefan Israelsson Tampe
2010-11-29 21:26                     ` http://gitorious.org/guile-scsh/guile-scsh Stefan Israelsson Tampe
2010-11-30 23:21                       ` Guile-Facade Ludovic Courtès
2010-11-25 21:26         ` The progress of hacking guile and prolog Ludovic Courtès
2010-11-26 16:41           ` Noah Lavine
2010-11-26 10:45         ` Andy Wingo
2010-11-20 11:26     ` Andy Wingo
2010-11-04 17:57   ` Stefan Israelsson Tampe
2010-11-05 21:19   ` Stefan Israelsson Tampe
2010-11-19 23:11     ` GLIL->C compilation Ludovic Courtès
2010-11-19 23:20       ` Stefan Israelsson Tampe
2010-11-19 23:56         ` Ludovic Courtès [this message]
2010-11-20 12:18           ` Andy Wingo

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=87mxp4vpek.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /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).