From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile 2.2 TODO
Date: Thu, 03 Oct 2013 23:27:11 +0200 [thread overview]
Message-ID: <874n8y3v0w.fsf@pobox.com> (raw)
In-Reply-To: <87vc2kztv1.fsf@pobox.com> (Andy Wingo's message of "Sun, 01 Sep 2013 13:03:46 +0200")
Hi,
On Sun 01 Sep 2013 13:03, Andy Wingo <wingo@pobox.com> writes:
> * Source information.
>
> The plan here would be to use DWARF. We don't use DWARF yet, so there
> are a few parts of this.
>
> - Add a DWARF parser; see the wip-dwarf branch for that.
>
> - Emit debugging info entries (DIEs) for each function in a
> compilation unit, into the .debug_info section. Initially they
> would be minimal, just having the function's address and maybe its
> name.
>
> - Add machinery to (system vm debug) to get a DIE for a procedure, if
> it is present.
>
> - Add a macro-instruction to the assembler that records source
> location info. Have the assembler collect this info.
>
> - Have the assembler write out source location info into a .debug_line
> section, and link the DIE to that info.
>
> - Add an appropriate interface to (system vm debug) to parse out line
> number information. Perhaps model this interface on what is already
> in (system vm program).
>
> - Shim the existing (system vm program) interfaces to call the new
> (system vm debug) interfaces for RTL programs.
Done! Woo hoo :)
> * Local variable information.
Still to do, will put off until later.
> * Replace bytecode trampolines with RTL trampolines.
> * Prompt, abort, and call/cc.
> * Compiling all of Guile to RTL.
These are next.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-10-03 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 11:03 Guile 2.2 TODO Andy Wingo
2013-09-01 19:07 ` Peter TB Brett
2013-09-02 20:01 ` Andy Wingo
2013-09-14 13:48 ` Ludovic Courtès
2013-09-17 20:16 ` Andy Wingo
2013-10-03 21:27 ` Andy Wingo [this message]
2013-10-18 9:56 ` Andy Wingo
2013-10-29 12:27 ` 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=874n8y3v0w.fsf@pobox.com \
--to=wingo@pobox.com \
--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).