unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: lightning <lightning@gnu.org>,
	Ian Grant <ian.a.n.grant@googlemail.com>,
	 guile-devel <guile-devel@gnu.org>
Subject: Re: Bug free programs
Date: Tue, 16 Sep 2014 20:57:48 -0400	[thread overview]
Message-ID: <20140917005748.8CXVB.21497.root@cdptpa-web03> (raw)
In-Reply-To: <CAKFjmdzBhVTDHJst-f_a+d3CeRzKckgmwvUmUbPsPJZfNgg3Qg@mail.gmail.com>


---- Ian Grant <ian.a.n.grant@googlemail.com> wrote: 

....

> One may ask what has this to do with scheme? Well, Standard ML can
> compose scheme or C code just as easily as it can compose assembler
> code. So a Standard ML functor can define a typed template that will
> allow one to exchange underling scheme implementations of functional
> interfaces as easily as it does ML. This is why I want to get Moscow
> ML working under Guile. Moscow ML is really light-weight when compared
> with Guile. My machine takes 42 minutes (no, really, I timed it!)  to
> byte-compile just ice9-pp.go. By comparison, the whole Moscow ML
> autoconf/build cycle takes less than 50s. This includes the runtime,
> the Standard ML basis library, and the lexer and parser generators and
> the compiler and toplevel REPL. And there's a fair bit of junk we
> could trip out, and we could make it a lot faster once we JIT compile
> the bytecode instead of interpreting it, and when that JIT compiled
> bytecode uses native Guile SCM objects to representall its data, then
> there will no penalty whatsoever in a Guile program just switching to
> Standard ML when it seems like a good idea.

Note that the 42 minutes here is a dumbed-down scheme interpreter written in C building/boostrapping the compiler.
The guile compiler (the Scheme one) is quite a bit faster than that.

-Dale





  parent reply	other threads:[~2014-09-17  0:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 22:38 Bug free programs Ian Grant
2014-09-16  9:20 ` Bootstrapping Ludovic Courtès
2014-09-17  0:57 ` dsmich [this message]
2014-09-17  1:22   ` Bug free programs Ian Grant
2014-09-17  3:27     ` Mark H Weaver
     [not found]       ` <8738brsz82.fsf-Ir+b6ulHfbb+AlalS6MPSg@public.gmane.org>
2014-09-17 13:35         ` Ian Grant
2014-09-17 17:29           ` Mark H Weaver
     [not found]             ` <87a95yp341.fsf-Ir+b6ulHfbb+AlalS6MPSg@public.gmane.org>
2014-09-17 18:11               ` Ian Grant
2014-09-17 21:32                 ` Ludovic Courtès
     [not found]                   ` <87sijq2arb.fsf-mXXj517/zsQ@public.gmane.org>
2014-09-17 22:10                     ` Ian Grant
2014-09-17 21:57               ` Ian Grant
     [not found]                 ` <CAKFjmdwA31CsB_FLYuOLBfR6_DX5Qj+GUGnoMxwgrBryy4Uqtw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-18  0:50                   ` Ian Grant
2014-09-17 16:15         ` Ian Grant
2014-09-18  9:28           ` Neil Jerram

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=20140917005748.8CXVB.21497.root@cdptpa-web03 \
    --to=dsmich@roadrunner.com \
    --cc=guile-devel@gnu.org \
    --cc=ian.a.n.grant@googlemail.com \
    --cc=lightning@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).