From: Mark H Weaver <mhw@netris.org>
To: Ian Price <ianprice90@googlemail.com>
Cc: 15533@debbugs.gnu.org
Subject: bug#15533: optimizing away noticeable effects
Date: Sat, 05 Oct 2013 16:28:02 -0400 [thread overview]
Message-ID: <87ioxba2el.fsf@netris.org> (raw)
In-Reply-To: <87bo33cybo.fsf@Kagami.home> (Ian Price's message of "Sat, 05 Oct 2013 20:27:55 +0100")
Ian Price <ianprice90@googlemail.com> writes:
> scheme@(guile-user)> ,optimize (define (foo f arg)
> (let* ((l '())
> (m (if (pair? arg)
> (begin
> (set! l (cdr arg))
> (car arg))
> arg)))
> (lambda () (apply f m l))))
> $14 = (define (foo f arg)
> (let ((m (if (pair? arg)
> (begin (begin (cdr arg) (if #f #f)) (car arg))
> arg)))
> (lambda () (f m))))
I can confirm that the same thing happens on the stable-2.0 branch.
Mark
next prev parent reply other threads:[~2013-10-05 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 19:27 bug#15533: optimizing away noticeable effects Ian Price
2013-10-05 20:28 ` Mark H Weaver [this message]
2013-10-05 20:45 ` Mark H Weaver
2013-10-06 6:39 ` Mark H Weaver
2013-10-06 7:36 ` Mark H Weaver
2013-10-07 16:55 ` Ian Price
2013-10-08 17:13 ` Ian Price
2013-10-23 10:16 ` Ian Price
2014-01-07 4:38 ` Ian Price
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=87ioxba2el.fsf@netris.org \
--to=mhw@netris.org \
--cc=15533@debbugs.gnu.org \
--cc=ianprice90@googlemail.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).