From: Andy Wingo <wingo@pobox.com>
To: No Itisnt <theseaisinhere@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Lua
Date: Fri, 04 Jun 2010 00:04:02 +0200 [thread overview]
Message-ID: <m3d3w7wz71.fsf@pobox.com> (raw)
In-Reply-To: <AANLkTikRLcR4ZDFLGKzvaJ_Xp0a5wYaL7PLF4ZwGX0wp@mail.gmail.com> (No Itisnt's message of "Thu, 3 Jun 2010 15:36:10 -0500")
On Thu 03 Jun 2010 22:36, No Itisnt <theseaisinhere@gmail.com> writes:
>> Not a known bug, no. Can you make a test case?
>
> Yes, attached. It appears to happen when (rnrs control) is used. This
> is with the latest master commit.
Thanks!
> It's not urgent, but Lua does mandate tail call optimization.
I think the basic thing would be the equivalent of:
(lambda args ... (return (foo bar ...)) ...)
=>
(lambda args
(let ((unique-tag (make-prompt-tag)))
(% unique-tag
(...
(abort-to-prompt unique-tag (lambda () (foo bar ...)))
...)
(lambda (unused-cont thunk) (thunk)))))
And from there the compiler would be resposible for removing the prompt,
if possible.
But, I could be totally misled here and there's some much more simple
solution.
> On a related note, what would be the best way to benchmark a compiler
> optimization? I see "benchmark-guile"; is there a way to easily run it
> with an optimization enabled and disabled? And maybe get some fancy
> charts and graphs, too?
Just running benchmark-guile before and after, I'm afraid... Once
they're in master, there's http://ossau.homelinux.net/~neil/.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-03 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 18:00 Lua No Itisnt
2010-05-22 21:04 ` Lua Ludovic Courtès
2010-06-03 8:32 ` Lua No Itisnt
2010-06-03 19:29 ` Lua Andy Wingo
2010-06-03 20:36 ` Lua No Itisnt
2010-06-03 22:04 ` Andy Wingo [this message]
2010-06-03 22:07 ` Lua Andy Wingo
2010-06-13 21:03 ` Lua No Itisnt
2010-06-14 20:50 ` Lua Andy Wingo
2010-06-15 2:51 ` Lua No Itisnt
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=m3d3w7wz71.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=theseaisinhere@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).