From: Bill Schottstaedt <bil@ccrma.Stanford.EDU>
Subject: compilation
Date: Tue, 23 Apr 2002 05:16:25 -0700 [thread overview]
Message-ID: <200204231216.FAA01993@cmn14.stanford.edu> (raw)
> is anybody from the Guile community right now hacking
> Hobbit or some other scheme-to-c compiler for Guile?
In a sense, yes (mentioned in an earlier msg to guile-user);
and I'm very interested in this problem in general -- I've
written a partial Common Lisp->C translator (and a very long time
ago, worked (in PDP-10 assembly language...) on the SAIL
compiler). I tried Hobbit but did not get much speed-up,
but as previously mentioned, my context is heavily numerical.
And I don't remember (this was a while ago and my memory is
unreliable) any support for "foreign" functions; since I
use Guile almost solely as an extension language, I have
to be able to call my own stuff. If it isn't included
in the optimized code, then there's no point... The other
problem here is that a "quick and dirty hack" like the one
I'm doing now provides 90% of what I need (in a couple
week's work), and I'm swamped (as is everyone) with
other things to do, so a big project to do it right doesn't
resonate. But, maybe I'd get seduced into helping once it got
started.
(My experience with the Lisp->C translator is that you regret
it in the long run: dynamic loading is an incredible pain,
debugging is next-to-impossible, files end up scattered
everywhere, etc.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-04-23 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 12:16 Bill Schottstaedt [this message]
2002-04-23 15:04 ` compilation Rob Browning
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=200204231216.FAA01993@cmn14.stanford.edu \
--to=bil@ccrma.stanford.edu \
/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).