From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: wip-rtl return location
Date: Fri, 03 Aug 2012 10:06:47 +0200 [thread overview]
Message-ID: <873944v1pk.fsf@pobox.com> (raw)
In-Reply-To: <CA+U71=OPKDCOWWSDXYW33GRzEoph2KYewNNKvPRWXSwVO_AnAQ@mail.gmail.com> (Noah Lavine's message of "Thu, 2 Aug 2012 18:21:02 -0400")
Hi Noah,
Thanks for the thoughts.
On Fri 03 Aug 2012 00:21, Noah Lavine <noah.b.lavine@gmail.com> writes:
> That sounds interesting, but I have a question - why not make the MVRA
> return address immediately after the call, instead of immediately
> before it? In the common case when returning to the regular return
> address, that would eliminate the extra branch (although it's a very
> small branch anyway).
It's a good idea; I have it in my local branch. Putting the MVRA before
the call didn't work out because the call instruction is
variable-length.
> CALL:
> call f
> MVRA:
> jump mv-handler
> RA:
> ... rest of function ...
Yes and for a truncating return:
CALL:
call f
MVRA:
truncate
RA:
... rest of function ...
Native compilation should do something different though. But Mark's
mail has more on that, so I'll reply there.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-08-03 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 14:29 wip-rtl return location Andy Wingo
2012-08-02 22:21 ` Noah Lavine
2012-08-03 8:06 ` Andy Wingo [this message]
2012-08-03 2:29 ` Mark H Weaver
2012-08-03 8:24 ` Andy Wingo
2012-08-03 11:54 ` Stefan Israelsson Tampe
2012-08-03 12:38 ` Andy Wingo
2012-08-03 13:13 ` Stefan Israelsson Tampe
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=873944v1pk.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@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).