unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: wip-rtl return location
Date: Fri, 3 Aug 2012 15:13:00 +0200	[thread overview]
Message-ID: <CAGua6m1kyCn9G+vpY0arBp2WQgSJGH60sTHck_+-Yw0WbdcDEA@mail.gmail.com> (raw)
In-Reply-To: <871ujotajy.fsf@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

 > in the normal case you just have
> assert-nargs-ee/locals which is very cheap, no?

Sure it's not the slowest of instructions, but in the VM it's an extra jump
and for the Native part it either bloats the code or one has to jump out
to supporting code subs in the VM. Considering the other call overhead
it's maybe a non issue but I think we should time current setup with a
version
where we grovel the callee information from the program datastructure.

/Stefan

On Fri, Aug 3, 2012 at 2:38 PM, Andy Wingo <wingo@pobox.com> wrote:

> On Fri 03 Aug 2012 13:54, Stefan Israelsson Tampe <stefan.itampe@gmail.com>
> writes:
>
> > A though:
> > assert_nargs_ee
> > reserve_locals
> > assert_nargs_ee_locals
> > bind_rest
> > bind_kwargs
> >
> > Could we not implement this logic in the call instructions?
>
> This is a characteristic of the callee -- more work is needed if there
> are optional/kw args, but in the normal case you just have
> assert-nargs-ee/locals which is very cheap, no?
>
> Andy
> --
> http://wingolog.org/
>

[-- Attachment #2: Type: text/html, Size: 1583 bytes --]

      reply	other threads:[~2012-08-03 13:13 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
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 [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=CAGua6m1kyCn9G+vpY0arBp2WQgSJGH60sTHck_+-Yw0WbdcDEA@mail.gmail.com \
    --to=stefan.itampe@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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).