From: Matt Hellige <matt@immute.net>
Subject: Re: Continuations: possible newbie question
Date: Wed, 18 Dec 2002 17:51:55 -0600 [thread overview]
Message-ID: <20021218175155.B25665@metro.immute.net> (raw)
In-Reply-To: <m3znr3ccvr.fsf@laruns.ossau.uklinux.net>; from neil@ossau.uklinux.net on Wed, Dec 18, 2002 at 08:04:24PM +0000
[Neil Jerram <neil@ossau.uklinux.net>]
> >>>>> "Matt" == Matt Hellige <matt@immute.net> writes:
>
> Matt> Well, at this point it definitely seems to be a bug.
>
> I tried your original code in my copy of stable branch Guile CVS
> (i.e. 1.6.x), and it worked as (you) expected.
>
> So either this has been fixed, in which case you could try the just
> released 1.6.1, or it is something trickier to pin down, in which case
> what platform are you using etc.?
>
Interesting. At first 1.6.1 showed the same behavior, but I got
suspicious that it was something about my config, and tried rebuilding
with different optimization settings. The problem went away.
I *believe* that the significant change was from -O3 to -O2. Based on
the little that I know about how guile is implemented, this doesn't
surprise me too much: I assume that the optimization somehow broke
guile's stack inspection magic. On the other hand, that could be way
off. As I said, I've been using guile (and scheme) for less than two
weeks now.
In any case, this is almost certainly not a bug in guile, but is it a
known issue with building? Is it documented anywhere that optimization
beyond -O2 may break guile? I couldn't find it in INSTALL, or anywhere
else, but I may have missed it. Perhaps it should be mentioned, as the
resulting behavior is definitely a bit mystifying. :)
On the other hand, I'll probably still not end up using this technique
to implement my call-backs, given the performance penalties and so on.
I hope I can just shuffle things around a bit in my native code...
Thanks very much for your help!
Matt
--
Matt Hellige matt@immute.net
http://matt.immute.net
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-12-18 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 17:27 Continuations: possible newbie question Thien-Thi Nguyen
2002-12-18 18:14 ` Matt Hellige
2002-12-18 20:04 ` Neil Jerram
2002-12-18 23:51 ` Matt Hellige [this message]
2002-12-19 0:41 ` Marius Vollmer
2002-12-19 2:42 ` Matt Hellige
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 18:42 Thien-Thi Nguyen
2002-12-18 0:14 Matt Hellige
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=20021218175155.B25665@metro.immute.net \
--to=matt@immute.net \
/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).