From: "Christoph Höger" <christoph.hoeger@tu-berlin.de>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Re-entrant OCaml
Date: Thu, 29 Dec 2016 18:46:43 +0100 [thread overview]
Message-ID: <a004616d-77ea-e690-ec6d-aa85f671cf64@tu-berlin.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1336 bytes --]
Dear all,
I am currently investigating a proprietary application server with an
embedded functional language. The current implementation of the language
misses several features and one particular interesting path for further
development would be to compile it to OCaml.
There is, however, the caveat of embedding the generated code in the
application server. Right now, (compiled) programs are called directly
from the core (effectively just C-functions) and call a certain API on
the core (again, C-functions). This is possible in OCaml, too, but the
default runtime is not thread-safe. If multiple such calls are made
concurrently, I expect immediate havoc.
Is there any project that provides a re-entrant runtime? In particular,
I would be interested in a version of libasmrun (and the corresponding
compiler) that does not rely on static variables. Instead, the required
data could be passed as an argument to each function.
Is there any such backend currently under development? How are the
chances of mainlining?
regards,
Christoph
--
Christoph Höger
Technische Universität Berlin
Fakultät IV - Elektrotechnik und Informatik
Übersetzerbau und Programmiersprachen
Sekr. TEL12-2, Ernst-Reuter-Platz 7, 10587 Berlin
Tel.: +49 (30) 314-24890
E-Mail: christoph.hoeger@tu-berlin.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2016-12-29 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 17:46 Christoph Höger [this message]
2016-12-29 18:26 ` Gabriel Scherer
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=a004616d-77ea-e690-ec6d-aa85f671cf64@tu-berlin.de \
--to=christoph.hoeger@tu-berlin.de \
--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