From: Andy Wingo <wingo@pobox.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Register VM WIP
Date: Wed, 16 May 2012 17:01:40 +0200 [thread overview]
Message-ID: <87mx58i2zv.fsf@pobox.com> (raw)
In-Reply-To: <CAGua6m0=cav13eX29vyTsAAf0KFdgRaO48_cmwY8mDBFqY5L-w@mail.gmail.com> (Stefan Israelsson Tampe's message of "Fri, 11 May 2012 22:29:11 +0200")
Hi Stefan,
On Fri 11 May 2012 22:29, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> 1. What about growing stacks any coments if they will be easier to manage
> for this setup. Can one copy the C stack logic?
Having a fixed-size frame means that it's easier to have disjoint
stacks, since a register VM addresses operands relative to the frame
pointer and not the stack pointer. I hope to be able to decrease our
default stack size, and allow it instead to grow dynamically.
> 2. Is there an instruction that does what call does but can be used for tail call's
> when it needs it e.g. the code
> for (n = 0; n < nargs; n++)
> LOCAL_SET (n, old_fp[ip[4 + n]]);
> that is missing for the tail code
This is another advantage of wip-rtl. In it, the compiler is
responsible for shuffling tail arguments. It can do a parallel move
possibly without shuffling args to the top of the stack. Then tail-call
just sets a new procedure and jumps to its entry.
> 3. I would appriciate if the frame is always below say 256 SCM:s of the fp stack limit
> that way when preparing tail calling one doesn't usally need to check if the argument fit's
> when issuing a tail call.
See above :)
> 4. I think the logic code hook I recently investigated could easily fit into this VM engine with
> using similar techniques as I described in previous mails.
I'm still working back through the mails; remind me again if it seems I
overlooked this mail.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-05-16 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 16:19 Register VM WIP Andy Wingo
2012-05-11 20:29 ` Stefan Israelsson Tampe
2012-05-16 15:01 ` Andy Wingo [this message]
2012-05-14 21:09 ` Ludovic Courtès
2012-05-14 21:28 ` Andrew Gwozdziewycz
2012-05-15 18:45 ` Andy Wingo
2012-05-16 0:39 ` Noah Lavine
2012-05-16 4:23 ` Mark H Weaver
2012-05-16 7:15 ` Andy Wingo
2012-05-16 13:44 ` Mark H Weaver
2012-05-16 14:00 ` David Kastrup
2012-05-16 14:54 ` Noah Lavine
2012-05-16 15:05 ` Andy Wingo
2012-05-16 20:39 ` Ludovic Courtès
2012-05-16 14:58 ` Andy Wingo
2012-05-16 16:27 ` Mark H Weaver
2012-05-16 16:39 ` Andy Wingo
2012-05-16 18:23 ` Noah Lavine
2012-05-16 7:10 ` Andy Wingo
2012-05-15 18:49 ` 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=87mx58i2zv.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@gmail.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).