unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 13809@debbugs.gnu.org
Subject: bug#13809: Wishlist: support > 10 args to foreign functions
Date: Mon, 25 Feb 2013 10:01:41 +0100	[thread overview]
Message-ID: <87a9qs937u.fsf@pobox.com> (raw)
In-Reply-To: <87621h6xkl.fsf@tines.lan> (Mark H. Weaver's message of "Sun, 24 Feb 2013 19:34:18 -0500")

On Mon 25 Feb 2013 01:34, Mark H Weaver <mhw@netris.org> writes:

> The current limitation of 10 arguments to foreign functions is proving
> to be a problem for some libraries, in particular the Allegro game
> library.
>
> Is there a reason why raising this limit to 16 or 20 would be
> undesirable?  What tradeoffs are involved?

Each arity of foreign functions gets a little VM program stub that
checks the argument count then actually does the call.  We statically
generate the first N of those arities (currently 10), and then for the
rest we should dynamically allocate the objcode stubs.  Dynamic
allocation is currently unimplemented.

We could raise the pregenerated size, but I think it would be better to
do the dynamic allocation thing.

Andy
-- 
http://wingolog.org/





  reply	other threads:[~2013-02-25  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25  0:34 bug#13809: Wishlist: support > 10 args to foreign functions Mark H Weaver
2013-02-25  9:01 ` Andy Wingo [this message]
2013-02-26 22:40   ` bug#13809: [PATCH] Support calling foreign functions of 10 or more arguments Mark H Weaver
     [not found]   ` <878v6azol2.fsf_-_@tines.lan>
2013-02-27  9:25     ` Andy Wingo
     [not found]     ` <87fw0ixg4p.fsf@pobox.com>
2013-02-27 22:11       ` Mark H Weaver
     [not found]       ` <87ppzlxv95.fsf@tines.lan>
2013-02-28  8:40         ` Andy Wingo
2013-02-28 11:40           ` Mark H Weaver

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=87a9qs937u.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=13809@debbugs.gnu.org \
    --cc=mhw@netris.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).