From: Benedikt Meurer <benedikt.meurer@googlemail.com>
To: caml-list@inria.fr
Subject: [Caml-list] ARM PIC/natdynlink support for ocamlopt
Date: Mon, 21 Nov 2011 19:01:45 +0100 [thread overview]
Message-ID: <316D923D-4E2E-4F37-93F6-716D4CB3D310@googlemail.com> (raw)
Hello,
I did some initial work to let ocamlopt emit position-independent code on ARM, which enables support for natdynlink on ARM. The patch and additional information is available at
http://caml.inria.fr/mantis/view.php?id=5404
with even more information at
http://caml.inria.fr/mantis/view.php?id=5049
So far I've tested the patch with QEMU and a NanosG20 ARM Board, and the patch seems to work and doesn't seem to cause noticeable performance hits. However, it would be useful to get some more testing and feedback.
The latest version is always available from the natdynlink-arm branch of my ocaml-experimental repository at
https://github.com/bmeurer/ocaml-experimental/tree/natdynlink-arm
greets,
Benedikt
reply other threads:[~2011-11-21 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=316D923D-4E2E-4F37-93F6-716D4CB3D310@googlemail.com \
--to=benedikt.meurer@googlemail.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).