Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Christoph Höger" <christoph.hoeger@celeraone.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Manually linking generated native code
Date: Thu, 19 Jan 2017 13:24:04 +0100	[thread overview]
Message-ID: <CAOazmvtTSuhiPaaRwwpaRcvM0dbOyRzJiK-jPD+N1_f6kzFpxg@mail.gmail.com> (raw)
In-Reply-To: <1484827880.14465.105.camel@gerd-stolpmann.de>

[-- Attachment #1: Type: text/plain, Size: 2449 bytes --]

Could you elaborate a little bit, how that should work? AFAIK, e.g. the
curry helpers are generated in Cmmgen, which is absolutely sensible, since
they certainly do not depend on the machine architecture, right? So when
and where does the linker use this generation?

To motivate my question a little bit, I was wondering whether I could load
two different OCaml executables inside the same process by using LLVM's
runtime linker. In principle, when I load them, they should be able to
cooperate across the shared heap, but otherwise live in total isolation (in
particular their garbage collectors should not interfere).

On Thu, Jan 19, 2017 at 1:11 PM, Gerd Stolpmann <info@gerd-stolpmann.de>
wrote:

> Am Donnerstag, den 19.01.2017, 10:44 +0100 schrieb Christoph Höger:
>
> Dear all,
>
> consider a simple test program:
>
>   let _ = Printf.printf "Hello world!\n"
>
> I can generate the relevant assembly just fine, e.g.:
>
> ocamlopt -dstartup -S test.ml
> gcc -c a.out.startup.s -c
>
> But I cannot link it:
>
> gcc a.out.startup.o -L$(ocamlc -where) -lasmrun_shared
> ....
> a.out.startup.o(.data+0x6e8): error: undefined reference to
> 'camlStd_exit__frametable'
> collect2: Fehler: ld gab 1 als Ende-Status zurück
> distcc[9960] ERROR: compile (null) on localhost failed
>
> It seems that the whole Pervasives is missing (which is kind of expected).
>
> How do I link it, manually? Where are the relevant object files?
>
>
> There's stdlib.a in the OCaml library directory.
>
> This is not the only problem with your approach. The OCaml linker
> generates a number of functions that are global to the whole OCaml program
> (in particular currying helpers). These are first known at link time and
> thus generated that late. AFAIK you cannot generate these functions outside
> the linker step.
>
> The only official way how to turn OCaml code into a linkable object is
> described here: http://caml.inria.fr/pub/docs/manual-ocaml/intfc.
> html#s%3Aembedded-code
>
> Gerd
>
>
> thanks,
>
> Christoph
>
> --
> ------------------------------------------------------------
> Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
> My OCaml site:          http://www.camlcity.org
> Contact details:        http://www.camlcity.org/contact.html
> Company homepage:       http://www.gerd-stolpmann.de
> ------------------------------------------------------------
>
>
>

[-- Attachment #2: Type: text/html, Size: 3686 bytes --]

  reply	other threads:[~2017-01-19 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19  9:44 Christoph Höger
2017-01-19 10:05 ` Bernhard Schommer
2017-01-19 12:11 ` Gerd Stolpmann
2017-01-19 12:24   ` Christoph Höger [this message]
2017-01-19 13:10     ` Gerd Stolpmann

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=CAOazmvtTSuhiPaaRwwpaRcvM0dbOyRzJiK-jPD+N1_f6kzFpxg@mail.gmail.com \
    --to=christoph.hoeger@celeraone.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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