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: instruction-level tracing
Date: Thu, 16 Sep 2010 22:29:49 +0200	[thread overview]
Message-ID: <877hill9du.fsf@gnu.org> (raw)
In-Reply-To: m3wrqmaqk9.fsf@unquote.localdomain

Hi Andy,

Andy Wingo <wingo@pobox.com> writes:

> I de-bitrotted instruction-level tracing in the VM. Ideally it would
> display like ,disassemble does, but that would take some more work.
>
> Still, Guile's speed is mostly proportional to how many instructions are
> executed, besides amount of garbage consed, and this view can be
> interesting to people looking to squeeze more performance out of their
> code, or find ways that the compiler does things wrong.
>
> scheme@(guile-user)> (use-modules (srfi srfi-1))
> scheme@(guile-user)> ,trace (fold cons '() '(a b c d)) #:instructions? #t

This looks like a useful tool, yes!

Thanks,
Ludo’.




      reply	other threads:[~2010-09-16 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 11:14 instruction-level tracing Andy Wingo
2010-09-16 20:29 ` Ludovic Courtès [this message]

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=877hill9du.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).