unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Arne Babenhauserheide <arne_bab@web.de>
To: guile-user@gnu.org
Subject: Re: How best to produce a standalone executable with Guile?
Date: Tue, 07 Apr 2020 23:30:48 +0200	[thread overview]
Message-ID: <87h7xv2dbr.fsf@web.de> (raw)
In-Reply-To: <CAB_RW2G85Gbo9g1q1X7zQ5cSxQe=6ayGnReue8aR6XNeGLr44A@mail.gmail.com>

Hi James,

James Cooper <jcoo092@aucklanduni.ac.nz> writes:
> Am I correct in understanding that guild essentially is what the Guile
> runtime will use to compile my source files before executing them?

Not quite. Guile does create bytecode, and guild can create it, but this
also happens during normal execution.

For some tasty details see https://wingolog.org/archives/2014/01/19/elf-in-guile

> traditional executable is that I'm planning to run comparative benchmarking
> directly on equivalent versions of the same program in different languages,
> and I *think *that will work a lot better if I can specify an executable

This sounds pretty interesting. Before you run this, though, please get
the help of experienced Guile programmers. I have an example of a
string-handling procedure which got more than 160x faster thanks to help
from others here. No typo there: It really got more than
hundred-and-sixty-times faster.

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken



  reply	other threads:[~2020-04-07 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05  5:28 How best to produce a standalone executable with Guile? James Cooper
2020-04-05 14:44 ` Matt Wette
2020-04-07  9:31 ` James Cooper
2020-04-07 21:30   ` Arne Babenhauserheide [this message]
     [not found] <mailman.85.1586102413.15610.guile-user@gnu.org>
2020-04-05 17:19 ` Christopher Howard

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=87h7xv2dbr.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-user@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).