From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: The Road to 2.2
Date: Mon, 20 May 2013 00:06:25 +0200 [thread overview]
Message-ID: <87fvxiwroe.fsf@gnu.org> (raw)
In-Reply-To: 878v3dgtv0.fsf@pobox.com
Hello!
This is all very exciting!
Andy Wingo <wingo@pobox.com> skribis:
> However, I think we've done all we can in branches. I think we should
> bless this RTL experiment as the way to do Guile 2.2. (Thoughts or
> objections welcome.) To that end, I think we need to start merging
> wip-rtl into master.
>
> What I propose is that, if we agree, I start merging in trivial stuff.
> When I get to something interesting that's not just a refactoring of
> existing things, I'll submit that patch to the list. We have a few days
> to look at it, we go through some review, and then we figure out how to
> move forward -- usually merging some version of that patch. Then we
> repeat.
Sounds like a good plan.
> Once the RTL branch is all merged in, we can start doing the same with
> Noah's wip-rtl-cps branch.
I’m unclear on what the safest or easiest approach is. My natural
tendency would have led me to start by “just” rewriting the
GLIL->assembly pass, and only then go with the fancy CPS compiler.
But I gather that the CPS compiler may facilitate the conversion to
assembly.
What’s your take on this?
> Then eventually some glorious day comes and we start using the CPS/RTL
> toolchain, everything is working great and fast, and we start deleting
> the old code.
Looking forward to that day. :-)
Ludo’.
next prev parent reply other threads:[~2013-05-19 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 21:49 The Road to 2.2 Andy Wingo
2013-05-18 5:00 ` Nala Ginrut
2013-05-18 10:37 ` Andy Wingo
2013-05-18 13:44 ` Noah Lavine
2013-05-18 15:18 ` Andy Wingo
2013-05-19 22:02 ` Ludovic Courtès
2013-05-22 4:23 ` Noah Lavine
2013-05-22 6:50 ` Nala Ginrut
2013-05-19 22:06 ` Ludovic Courtès [this message]
2013-05-20 14:33 ` 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=87fvxiwroe.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).