Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Christoph Sieghart <sigi@0x2a.at>
To: caml-list@yquem.inria.fr
Subject: Ocaml .cmo fileformat before linking
Date: Sat, 5 May 2007 23:15:57 +0000	[thread overview]
Message-ID: <20070505231556.GA911@harlekin> (raw)

Hello list,

I am writing an Ocaml interpreter for an embedded plattform (AVR) and now I
am searching for any material concerning the structure of the .cmo files before
linking happens. I compile my Ocaml files with 
 
 ocaml -c myfile.ml

an then extract the bytecode from there. I found documenation on the bytecode
(I already have an interpreter running on my plattform - no gc, no floating point
, no closures, no enviroment access) but not on the data that follows it in the .cmo file. 

The plan is to use the not linked .cmo files to extract the bytecode and the
data from and to supply a minimal library in the interpreter, because I am operating 
under tight memory constraints.

I would be glad for any pointers, best regards
Christoph


                 reply	other threads:[~2007-05-05 21:15 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=20070505231556.GA911@harlekin \
    --to=sigi@0x2a.at \
    --cc=caml-list@yquem.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