From: Andy Wingo <wingo@pobox.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guile-user@gnu.org, Matt Wette <matt.wette@gmail.com>
Subject: Re: Stack traces
Date: Fri, 19 May 2017 11:17:15 +0200 [thread overview]
Message-ID: <87pof5mcis.fsf@pobox.com> (raw)
In-Reply-To: <87vaoy709i.fsf@dustycloud.org> (Christopher Allan Webber's message of "Thu, 18 May 2017 08:38:49 -0500")
On Thu 18 May 2017 15:38, Christopher Allan Webber <cwebber@dustycloud.org> writes:
> I frequently find that ,locals does not display much information... it
> seems to be a toss-up whether the variables I need will be contained
> in it, so I've reduced the amount I use the actual debugger system in
> Guile a lot. A shame, because it seems really nice.
This is related to the "basic register allocation" task from
https://wingolog.org/archives/2016/02/04/guile-compiler-tasks.
> But then I ran ,optimize, and that made it obvious what's happening:
Ah, yes you might also have to disable partial evaluation. Note that
,optimize basically runs only partial evaluation and not the other
phases of the compiler.
> scheme@(guile-user)> ,optimize-less
> scheme@(guile-user)> ,optimize-more
Not a bad idea :) Probably should use the same mechanism as "guild
compile"'s -O0, -O1, -O2 etc logic.
Andy
next prev parent reply other threads:[~2017-05-19 9:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.52572.1487077879.22737.guile-user@gnu.org>
2017-02-14 17:24 ` guile-user Digest, Vol 171, Issue 14 Cecil McGregor
2017-02-14 19:19 ` Christopher Allan Webber
2017-02-14 22:00 ` Amirouche
2017-02-14 22:16 ` Stack traces Ludovic Courtès
2017-02-15 15:36 ` Christopher Allan Webber
2017-02-16 1:10 ` Matt Wette
2017-02-18 0:13 ` Matt Wette
2017-02-18 15:50 ` Amirouche
2017-02-18 15:53 ` Amirouche
2017-02-18 16:58 ` Matt Wette
2017-02-18 19:59 ` Amirouche
2017-02-18 20:31 ` Matt Wette
2017-02-27 20:23 ` Andy Wingo
2017-02-27 20:40 ` Amirouche
2017-05-18 13:38 ` Christopher Allan Webber
2017-05-19 3:05 ` Matt Wette
2017-05-19 9:17 ` Andy Wingo [this message]
2017-06-10 9:58 ` Catonano
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=87pof5mcis.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).