From: Alain Frisch <alain@frisch.fr>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Using OCaml's run-time from LLVM-generated native code
Date: Mon, 04 Feb 2008 08:03:17 +0100 [thread overview]
Message-ID: <47A6B8B5.9010907@frisch.fr> (raw)
In-Reply-To: <200802032319.15846.jon@ffconsultancy.com>
Jon Harrop wrote:
> How does OCaml's stack walker work with C code, for example? In particular,
> how does it know what is a pointer into the heap from a C stack frame? Must
> it be explicitly disabled?
The OCaml runtime does not scan the stack frames corresponding to C
functions.
Jon, it is somewhat weird that you spend so much time writing about
forking OCaml and do not take a few minutes to read the source code. The
macros CAMLparam*, CAMLlocal* are not really that mysterious.
-- Alain
next prev parent reply other threads:[~2008-02-04 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 21:24 Jon Harrop
2008-02-03 21:24 ` [Caml-list] " Alain Frisch
2008-02-03 23:19 ` Jon Harrop
2008-02-04 7:03 ` Alain Frisch [this message]
2008-02-04 10:32 ` Jon Harrop
2008-02-04 11:11 ` Alain Frisch
2008-02-04 13:36 ` Jon Harrop
2008-02-04 15:20 ` Alain Frisch
2008-02-05 23:08 ` Florent Monnier
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=47A6B8B5.9010907@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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 NNTP newsgroup(s).