From: Ian Price <ianprice90@googlemail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 15533@debbugs.gnu.org
Subject: bug#15533: optimizing away noticeable effects
Date: Mon, 07 Oct 2013 17:55:36 +0100 [thread overview]
Message-ID: <877gdpc96f.fsf@Kagami.home> (raw)
In-Reply-To: <87siwe97gy.fsf@netris.org> (Mark H. Weaver's message of "Sun, 06 Oct 2013 03:36:13 -0400")
Mark H Weaver <mhw@netris.org> writes:
> Using git bisect, I've determined that this bug was introduced in the
> following commit:
>
> commit d21537efb4a0edea30a7ab801909207d4bb69030
> Author: Andy Wingo <wingo@pobox.com>
> Date: Fri Feb 15 12:11:29 2013 +0100
>
> better inlining of `apply' with rest arguments
>
> * module/language/tree-il/peval.scm (peval): Move up the find-definition
> helper. Use it to speculatively destructure conses and lists into the
> tail position of an `apply' form.
>
> * test-suite/tests/peval.test ("partial evaluation"): Add tests.
Thanks for bisecting mark, I've had a little look and this is the right
patch. The actual error occurs at the very beginning of the loop, in the
variable tail*.
Originally, this was a call (for-value tail), which returned a
lexical-ref. Now it is a call (find-definition tail) which returns a
const ().
We obviously need to have a check for mutability when referring to a
variable, the question is where?
Does it make sense to add it to find-definition? or should we add it
before the use in that case?
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2013-10-07 16:55 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
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 [this message]
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=877gdpc96f.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=15533@debbugs.gnu.org \
--cc=mhw@netris.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).