From: Markus Mottl <markus@oefai.at>
To: David Brown <caml-list@davidb.org>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Memory leak with native code.
Date: Thu, 5 Dec 2002 20:14:55 +0100 [thread overview]
Message-ID: <20021205191455.GA7580@fichte.ai.univie.ac.at> (raw)
In-Reply-To: <20021205184846.GA30014@opus.davidb.org>
On Thu, 05 Dec 2002, David Brown wrote:
> I guess what would be helpful would be any pointers on what might be
> different between bytecode and native. I do use callbacks, but the
> main program is in Ocaml.
Have you made sure that stubs taking more than five arguments need to
be split up into two functions? E.g.:
C-file:
CAMLprim value add_nat_native(value nat1, value ofs1, value len1,
value nat2, value ofs2, value len2,
value carry_in)
{
...
}
CAMLprim value add_nat_bytecode(value * argv, int argn)
{
return add_nat_native(argv[0], argv[1], argv[2], argv[3],
argv[4], argv[5], argv[6]);
}
OCaml-file:
external add_nat: nat -> int -> int -> nat -> int -> int -> int -> int
= "add_nat_bytecode" "add_nat_native"
Notice that the external function needs to be declared such on the
OCaml-side that you name both entry points (for byte- and native code).
That's the only difference that comes to my mind...
Regards,
Markus Mottl
--
Markus Mottl markus@oefai.at
Austrian Research Institute
for Artificial Intelligence http://www.oefai.at/~markus
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-12-05 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 18:48 David Brown
2002-12-05 19:14 ` Markus Mottl [this message]
2002-12-05 20:31 ` Basile STARYNKEVITCH
2002-12-07 10:42 ` Xavier Leroy
2002-12-07 21:52 ` David Brown
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=20021205191455.GA7580@fichte.ai.univie.ac.at \
--to=markus@oefai.at \
--cc=caml-list@davidb.org \
--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