caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
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 16:20:35 +0100	[thread overview]
Message-ID: <47A72D43.30204@frisch.fr> (raw)
In-Reply-To: <200802041336.22550.jon@ffconsultancy.com>

Jon Harrop wrote:
> On Monday 04 February 2008 11:11:33 Alain Frisch wrote:
>> Jon Harrop wrote:
>>> Despite the availability of that code it seems that few people can use it
>>> correctly and I am one of them.
>> What part of memory.h do you fail to understand?
> 
> That file doesn't even mention the stack walker AFAICT.

Nevertheless, the file contains all the info you need to produce GC-safe 
C code. If you want efficient GC-safe code, you need to understand how 
ocamlopt records information about stack frames. It is probably 
impossible to do it with pure portable C code. For LLVM-generated code, 
you should be able to use the GC infrastructure improved by Gordon.

> Perhaps this does:
> 
> int apply(int n) {
>   CAMLparam0();
>   CAMLlocal2(nv, fibn);
>   nv = copy_int64(n);
>   fibn = fib(nv);
>   caml_gc_full_major(0);
>   CAMLreturn(Int64_val(fib(nv)));
> }

CAMLreturnT would be better.


-- Alain


  reply	other threads:[~2008-02-04 15:20 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
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 [this message]
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=47A72D43.30204@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).