From: David Brown <caml-list@davidb.org>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Aaron Bohannon <bohannon@seas.upenn.edu>, caml-list@inria.fr
Subject: Re: [Caml-list] native code and ZINC machine
Date: Sat, 6 Nov 2004 08:53:23 -0800 [thread overview]
Message-ID: <20041106165323.GA12633@old.davidb.org> (raw)
In-Reply-To: <20041106093748.GA26835@yquem.inria.fr>
On Sat, Nov 06, 2004 at 10:37:48AM +0100, Xavier Leroy wrote:
> The ZINC / OCaml VM handling of curried function application (an
> instance of the push-enter model) pretty much requires that parameters
> are passed on a stack. For native code generation, it is much more
> efficient to pass the first N parameters in processor registers. This
> doesn't fit the ZINC model at all.
Just out of curiosity, what model does the native compiler use when
evaluating functions of unknown arity (List.map for example).
Dave
next prev parent reply other threads:[~2004-11-06 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 14:25 Aaron Bohannon
2004-11-06 9:37 ` [Caml-list] " Xavier Leroy
2004-11-06 16:53 ` David Brown [this message]
2004-11-08 8:52 ` Diego Olivier Fernandez Pons
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041106165323.GA12633@old.davidb.org \
--to=caml-list@davidb.org \
--cc=Xavier.Leroy@inria.fr \
--cc=bohannon@seas.upenn.edu \
--cc=caml-list@inria.fr \
/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