From: Noah Lavine <noah.b.lavine@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: [Guile-commits] GNU Guile branch, wip-rtl-cps, updated. v2.1.0-180-g0d0808a
Date: Tue, 19 Feb 2013 09:28:56 -0500 [thread overview]
Message-ID: <CA+U71=O_p2A9jkxbqV4aESThKVqvumuzYRK9ucatW2TO5+LiNw@mail.gmail.com> (raw)
In-Reply-To: <CA+U71=PzgEjJbLZ4vJm+CL-U0z2KW1NgNjWuj6B+nW4_eTMmqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
Oh, and thanks a lot for reviewing the CPS stuff! I really appreciate it,
and I think it will make the end result a lot better than whatever I could
do on my own.
Noah
On Tue, Feb 19, 2013 at 9:28 AM, Noah Lavine <noah.b.lavine@gmail.com>wrote:
> Hello,
>
> Yes, I completely agree with this. I didn't do that immediately because
> I'm trying to get the infrastructure for the general case working. I plan
> to implement un-boxing in CPS. The real reason not to do it yet is that the
> tree-il-CPS compiler can't compile any examples that would actually need
> boxes. (But it will be able to soon!)
>
> Noah
>
>
> On Tue, Feb 19, 2013 at 12:53 AM, Mark H Weaver <mhw@netris.org> wrote:
>
>> Hi Noah,
>>
>> "Noah Lavine" <noah.b.lavine@gmail.com> writes:
>> > commit 0d0808ae3f7390ffb250b9deb6706ad4158cce0e
>> > Author: Noah Lavine <noah.b.lavine@gmail.com>
>> > Date: Mon Feb 18 14:10:58 2013 -0500
>> >
>> > Make Lambda Arguments Mutable
>> >
>> > * module/language/cps.scm: let variable objects come with an
>> > initialization value.
>> > * module/language/tree-il/compile-cps.scm: put all lambda arguments
>> in
>> > variable boxes, so they are mutable.
>>
>> Lambda arguments (and all other lexical variables) should only be put
>> into boxes if they are 'set!' somewhere within their lexical scope.
>> This can always be determined at compile time. It is crucial that we
>> minimize the number of mutable variables, since they inhibit most
>> optimizations.
>>
>> The required analysis is already implemented in tree-il/analyze.scm.
>>
>> Regards,
>> Mark
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2639 bytes --]
next prev parent reply other threads:[~2013-02-19 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1U7W96-0008Mr-Ei@vcs.savannah.gnu.org>
2013-02-19 5:53 ` [Guile-commits] GNU Guile branch, wip-rtl-cps, updated. v2.1.0-180-g0d0808a Mark H Weaver
2013-02-19 14:28 ` Noah Lavine
2013-02-19 14:28 ` Noah Lavine [this message]
2013-02-19 16:03 ` Mark H Weaver
2013-02-19 16:57 ` Noah Lavine
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='CA+U71=O_p2A9jkxbqV4aESThKVqvumuzYRK9ucatW2TO5+LiNw@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@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).