From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 10756@debbugs.gnu.org
Subject: bug#10756: [2.0.5+] Miscompilation with peval: local shadows module-ref
Date: Thu, 09 Feb 2012 14:17:22 +0100 [thread overview]
Message-ID: <8739ak16zh.fsf@pobox.com> (raw)
In-Reply-To: <87aa4ufdp1.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 08 Feb 2012 00:04:10 +0100")
On Wed 08 Feb 2012 00:04, ludo@gnu.org (Ludovic Courtès) writes:
> scheme@(guile-user)> ,optimize (define (foo) (define bar (@ (chbouib) bar)) bar)
> $11 = (define foo
> (lambda ()
> (let ((bar-1510 (if #f #f)))
> (letrec*
> ()
> (begin (set! bar-1510 bar-1510) bar-1510)))))
>
> Here, the ‘bar’ local is always set to *undefined*, wrongfully.
It's actually an expander bug:
scheme@(guile-user)> ,expand (define (foo) (define bar (@ (chbouib) bar)) bar)
$2 = (define foo
(lambda () (letrec* ((bar-92 bar-92)) bar-92)))
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-02-09 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 23:04 bug#10756: [2.0.5+] Miscompilation with peval: local shadows module-ref Ludovic Courtès
2012-02-09 13:17 ` Andy Wingo [this message]
2012-03-08 7:11 ` Mark H Weaver
2012-07-06 18:20 ` Andy Wingo
2012-03-08 7:13 ` Mark H Weaver
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=8739ak16zh.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10756@debbugs.gnu.org \
--cc=ludo@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).