From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH 10/10] add new rtl vm
Date: Thu, 30 May 2013 18:06:38 +0200 [thread overview]
Message-ID: <871u8owiy9.fsf@gnu.org> (raw)
In-Reply-To: 1369315863-15879-11-git-send-email-wingo@pobox.com
Hello!
Andy Wingo <wingo@pobox.com> skribis:
> * libguile/vm-engine.c (rtl_vm_engine): Add new VM.
> (vm_engine): Add support for calling RTL programs.
>
> * libguile/tags.h (scm_tc7_rtl_program): New type for procedures that
> run on the new VM.
> * libguile/evalext.c (scm_self_evaluating_p):
> * libguile/goops.c (scm_class_of):
> * libguile/print.c (iprin1):
> * libguile/procprop.c (scm_i_procedure_arity):
> * libguile/procs.c (scm_procedure_p): Add hooks for the new tc7.
>
> * libguile/programs.h:
> * libguile/programs.c (scm_make_rtl_program, scm_i_rtl_program_print)
> (scm_rtl_program_p, scm_rtl_program_code):
> * module/system/vm/program.scm: Add constructors and accessors for the
> new "RTL programs".
>
> * libguile/vm.c (rtl_boot_continuation): Define a boot program.
> (rtl_apply, rtl_values): New static RTL programs.
>
> * libguile/frames.c (scm_frame_num_locals): Adapt for frames of RTL
> programs.
>
> * libguile/frames.h: Add description of RTL frames.
>
> * libguile/Makefile.am: Add rules to generate vm-operations.h.
> * .gitignore: Ignore vm-operations.h.
> * module/system/vm/instruction.scm:
> * libguile/instructions.c:
> * libguile/instructions.h: Use vm-operations.h to define enumerated
> values for the new RTL opcodes. Define some helper macros to pack and
> unpack 32-bit instruction words.
> (rtl-instruction-list): New function, exported by (system vm
> instruction).
>
> * libguile/objcodes.c: Wire up the bits needed to detect the new RTL
> bytecode and load it, as appropriate.
Sorry for the long delay. It all looks nice to me, and the ability of
have a transition with the two VMs side-by-side during the 2.1 series is
a convenient way to allow for further development of the new VM while
still allowing people to play with the other new features of 2.1.
That’s all I have to say now. Go ahead! :-)
Ludo’.
prev parent reply other threads:[~2013-05-30 16:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 13:30 Add RTL VM Andy Wingo
2013-05-23 13:30 ` [PATCH 01/10] inline vm-engine.h into vm-engine.c Andy Wingo
2013-05-23 21:28 ` Ludovic Courtès
2013-05-23 13:30 ` [PATCH 02/10] remove CONS macro in VM; use scm_cons instead Andy Wingo
2013-05-23 13:30 ` [PATCH 03/10] minor vm-engine cleanups Andy Wingo
2013-06-06 6:48 ` Marijn
2013-05-23 13:30 ` [PATCH 04/10] remove some configurability in vm-engine Andy Wingo
2013-05-23 13:30 ` [PATCH 05/10] vm-engine: remove register assignments Andy Wingo
2013-05-23 13:30 ` [PATCH 06/10] Allow vm_engine caller to pass arguments on the stack Andy Wingo
2013-05-23 21:37 ` Ludovic Courtès
2013-05-23 13:31 ` [PATCH 07/10] pop-continuation abort-continuation hooks pass return vals directly Andy Wingo
2013-05-23 21:46 ` Ludovic Courtès
2013-05-23 13:31 ` [PATCH 08/10] cpp hygiene in the vm Andy Wingo
2013-05-23 13:31 ` [PATCH 09/10] refactor to resolve_variable Andy Wingo
2013-05-23 21:47 ` Ludovic Courtès
2013-05-23 13:31 ` [PATCH 10/10] add new rtl vm Andy Wingo
2013-05-30 16:06 ` Ludovic Courtès [this message]
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=871u8owiy9.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).