From: Nala Ginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: RTL has landed!
Date: Mon, 11 Nov 2013 13:32:40 +0800 [thread overview]
Message-ID: <1384147960.2914.21.camel@Renee-desktop.suse> (raw)
In-Reply-To: <87bo1t7kze.fsf@pobox.com>
On Sat, 2013-11-09 at 14:39 +0100, Andy Wingo wrote:
> Hi!
>
> Just a brief note to say that if you haven't noticed, the "master"
> branch of Guile now compiles to the new virtual machine, using the new
> compiler. All tests pass. The old VM is gone!
>
Congrats!
> There are a couple of regressions that I would like to fix soonish:
>
> * The compiler is somewhat slow. I haven't tried to optimize it at
> all, so there's lots to do here. To a degree it is to be expected,
> as the compiler does more work -- but I hope to get it faster than
> the 2.0 compiler.
>
> * We don't have local variable information. In the debugger, ,locals
> doesn't print anything. Here we need to build this information at
> compile-time, write it into ELF somehow (perhaps using DWARF), and
> read it out as needed at runtime. I'll take a look at this too.
>
> * The manual is out of date, as regards the compiler and VM.
>
> Besides these regressions, there are a many optimizations to make --
> many more than before -- now that we have a better intermediate language
> in which to express them.
>
> Let the list know if you find any problems that aren't covered by the
> test suite.
>
> I hope we can get out a 2.1.0 release -- which would be a prerelease for
> 2.2 -- around mid-December or so. We can aim for 2.2.0 for next May or
> so, but that's a totally fictional date I just made up :)
>
Next May sounds nice, but no rush anyway IMO ;-)
Thanks for working on it!
> Cheers,
>
> Andy
next prev parent reply other threads:[~2013-11-11 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 13:39 RTL has landed! Andy Wingo
2013-11-11 5:32 ` Nala Ginrut [this message]
2014-03-24 21:45 ` 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=1384147960.2914.21.camel@Renee-desktop.suse \
--to=nalaginrut@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).