From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: wip-rtl disassembler
Date: Tue, 7 May 2013 00:16:40 -0400 [thread overview]
Message-ID: <CA+U71=PRUXgeQnjgSQ=NFG3zDaa7p2RhOmTePSC=OYaYO9RxyA@mail.gmail.com> (raw)
In-Reply-To: <87ppx5rxke.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Sun, May 5, 2013 at 4:17 PM, Andy Wingo <wingo@pobox.com> wrote:
> At this point the disassembler is working much better, and works at the
> REPL now via ,x. Also, procedure-name now works.
>
> I'm now moving to implement source line information and other metadata
> via .debug_info / .debug_line / etc sections.
>
Wow, that's great!
> I think debugging things will be ready in a few weeks. Noah, how's the
> compiler coming? I think we could reasonably be looking at compiling
> everything with RTL by July or August if all goes well.
>
Not as quickly as I'd like, but that's always going to be true. :-)
The status is still what it was in my last email - almost all language
features are done, but I would like to check edge cases much more
thoroughly than I have. What I have been working on most recently is a
patch to the test suite to add a command-line option to choose a different
compiler. I realized that my strategy of writing a separate test suite for
CPS will never get close to our 35,000+ Guile tests, and also can't be
reused the next time we want to test a new compiler. So my goal is to let
the test suite use the CPS compiler, and then just systematically fix any
bugs I find until things pass.
If anyone else wants to work on this, they are more than welcome to jump in.
Noah
[-- Attachment #2: Type: text/html, Size: 1952 bytes --]
next prev parent reply other threads:[~2013-05-07 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 8:11 wip-rtl disassembler Andy Wingo
2013-05-02 12:59 ` Noah Lavine
2013-05-05 20:17 ` Andy Wingo
2013-05-07 4:16 ` Noah Lavine [this message]
2013-05-07 16:52 ` Ludovic Courtès
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=PRUXgeQnjgSQ=NFG3zDaa7p2RhOmTePSC=OYaYO9RxyA@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@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).