From: Norman Hardy <norm@cap-lore.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Compiled code that uses the stack when it can.
Date: Mon, 5 Nov 2012 11:21:13 -0800 [thread overview]
Message-ID: <20D75025-C0A1-43A0-89BE-30AD5ED04545@cap-lore.com> (raw)
Is there a way to get ocamlopt to leave the C sources behind?
Does ocamlopt ever use the stack to call functions that it compiled?
Does anyone know of compilers that use the stack when they can but uses the heap when it must?
Is there literature on this?
This slide set is very useful but seems to suggest that internal functions representations are treated uniformly.
http://pauillac.inria.fr/~xleroy/talks/compilation-agay.pdf
I am thinking about static code analysis to determine two or perhaps three ways free variables in a function might be handled.
It is hard enough that I would like to see if it has been done before.
next reply other threads:[~2012-11-05 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 19:21 Norman Hardy [this message]
2012-11-05 19:33 ` AW: " Gerd Stolpmann
2012-11-05 22:25 ` Pierre Chambart
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=20D75025-C0A1-43A0-89BE-30AD5ED04545@cap-lore.com \
--to=norm@cap-lore.com \
--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;
as well as URLs for NNTP newsgroup(s).