From: Andy Wingo <wingo@pobox.com>
To: "Steven H. Margolis" <shm@pobox.com>
Cc: 19389@debbugs.gnu.org
Subject: bug#19389: visit-entry argument problem in module/language/cps/verify.scm
Date: Wed, 22 Jun 2016 21:37:29 +0200 [thread overview]
Message-ID: <878txxrp52.fsf@pobox.com> (raw)
In-Reply-To: <E50C2E8E-37EB-46C1-8681-628E6902A141@pobox.com> (Steven H. Margolis's message of "Mon, 15 Dec 2014 08:18:31 -0800")
Thank you Steven! I really appreciate you trying out the development
branch so early, and I apologize that I wasn't able to acknowledge the
report then. When you reported I think I wasn't thinking about the
issue because I was in the middle of the transition to the "cps soup"
IR, which ended up eliminating this bug through other means, so I will
close this report. Please let us know if you find problems in the
future; reports are very welcome.
Regards,
Andy
On Mon 15 Dec 2014 17:18, "Steven H. Margolis" <shm@pobox.com> writes:
> This weekend I noticed a build problem in guile from the savannah git repository. I think the patch below is an appropriate fix:
>
> (08:06:43 <~/OpenSource/guile2/guile-savannah>) 0 $ git diff
> diff --git a/module/language/cps/verify.scm b/module/language/cps/verify.scm
> index a39e99b..b636fc4 100644
> --- a/module/language/cps/verify.scm
> +++ b/module/language/cps/verify.scm
> @@ -129,7 +129,7 @@
> (match fun
> (($ $fun (free ...) entry)
> (for-each (cut check-var <> v-env) free)
> - (visit-entry '() v-env))
> + (visit-entry '() k-env v-env))
> (_
> (error "unexpected $fun" fun))))
next prev parent reply other threads:[~2016-06-22 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 16:18 bug#19389: visit-entry argument problem in module/language/cps/verify.scm Steven H. Margolis
2016-06-22 19:37 ` Andy Wingo [this message]
2016-06-22 19:37 ` bug#19389: Status: " Andy Wingo
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=878txxrp52.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=19389@debbugs.gnu.org \
--cc=shm@pobox.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).