From: r0ller@freemail.hu
To: fa.caml@googlegroups.com
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
Francois Berenger <berenger@riken.jp>,
caml-list@inria.fr
Subject: Re: [Caml-list] ocamlc compiles hello world, ocamlopt not
Date: Wed, 16 Jan 2013 02:16:15 -0800 (PST) [thread overview]
Message-ID: <160aed40-5e04-41e2-ba4c-f78b8b270f24@googlegroups.com> (raw)
In-Reply-To: <fa.3ZA77VqUCTh0CDJf/dKc9fxM234@ifi.uio.no>
Hi Basile,
Thanks! I'll definitely have a look at it even though compiling a whole ocaml project will be challenging:) Yet another really bold question: I do not know, how the original ocamlopt is built but if it's also built from bytecode, can ocamlcc be used to build ocamlopt?
Thanks®ards,
r0ller
On Wednesday, January 16, 2013 10:48:36 AM UTC+1, Basile Starynkevitch wrote:
> On Wed, Jan 16, 2013 at 10:01:06AM +0100, Gerd Stolpmann wrote:
>
> > Am 16.01.2013 09:56:55 schrieb(en) Francois Berenger:
>
> > >On 01/16/2013 05:02 PM, r0ller@.hu wrote:
>
> > >>Hi All,
>
> > >>
>
> > >>By the way, is there any doc available about porting ocaml
>
> > >>(google didn't find any) or any hint on how to move forward? I'd
>
> > >>really like to have the native compiler on minix too.
>
> > >
>
> > >I think in the past it was possible to generate C code from OCaml
>
> > >code.
>
> >
>
> > There is no real C backend (and has never been). The only thing you
>
> > can do is to embed bytecode in a C-friendly way (what -output-obj
>
> > does). But it is still bytecode.
>
>
>
>
>
> Benoit Vaugon & Michel Mauny worked recently on OcamlCC
>
> (a translator from Ocaml bytecode to C)
>
> http://oud.ocaml.org/2012/abstracts/oud2012-final10.pdf
>
> https://github.com/ocaml-bytes/ocamlcc
>
>
>
> Cheers.
>
> --
>
> Basile STARYNKEVITCH http://starynkevitch.net/Basile/
>
> email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
>
> 8, rue de la Faiencerie, 92340 Bourg La Reine, France
>
> *** opinions {are only mines, sont seulement les miennes} ***
>
>
>
> --
>
> Caml-list mailing list. Subscription management and archives:
>
> https://sympa.inria.fr/sympa/arc/caml-list
>
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2013-01-16 10:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.tMEIU2eZ10ydMQJpEId8zYmuWpo@ifi.uio.no>
[not found] ` <fa.5ytRg9PGwzfRT5U12a+96CThPHM@ifi.uio.no>
[not found] ` <fa.fEvQzwMsL9tn+Q+kKoqZrwKQpHs@ifi.uio.no>
[not found] ` <fa.gj9h88pWsiKoDqywSvikWobc2Gk@ifi.uio.no>
[not found] ` <fa.yuD604fWUWzMhQKQ2PVUY9+PSRs@ifi.uio.no>
[not found] ` <fa.SiWjqBgSRaJHHtRDr1LQlRGec/I@ifi.uio.no>
2013-01-16 9:29 ` r0ller
[not found] ` <fa.vGYTX053VB/7kO+WVlnBXs6LyWM@ifi.uio.no>
2013-01-16 9:36 ` r0ller
2013-01-16 9:53 ` AW: " Gerd Stolpmann
[not found] ` <fa.3ZA77VqUCTh0CDJf/dKc9fxM234@ifi.uio.no>
2013-01-16 10:16 ` r0ller [this message]
[not found] ` <fa.AgEvtE0xHcqZGBKj0Yv0NqpqfDI@ifi.uio.no>
[not found] ` <fa.U9QIrhkTeSswG97/yP/PR0sEGRA@ifi.uio.no>
2013-01-17 13:06 ` r0ller
[not found] <fa.rDSh+u4grOqB/jgTnZaDUQoT+s0@ifi.uio.no>
[not found] ` <fa.53tG84D0PDsZ/dZaWLkOQvsLfTU@ifi.uio.no>
2013-01-16 10:20 ` r0ller
[not found] <fa.J86NbZyp4NcoVDLx3IIZPjh6Xsw@ifi.uio.no>
[not found] ` <fa.cI6IwITMmpEcG/xX8jnbm1tXnWU@ifi.uio.no>
2013-01-11 16:13 ` r0ller
2013-01-11 16:23 ` r0ller
2013-01-16 8:02 ` r0ller
2013-01-16 8:56 ` Francois Berenger
2013-01-16 9:01 ` AW: " Gerd Stolpmann
2013-01-16 9:48 ` Basile Starynkevitch
2013-01-16 22:32 ` Benedikt Meurer
2013-01-16 23:17 ` Gabriel Scherer
2013-01-17 19:34 ` Benedikt Meurer
2013-01-10 14:48 r0ller
2013-01-10 16:08 ` Gerd Stolpmann
2013-01-11 9:28 ` r0ller
2013-01-11 9:56 ` Xavier Leroy
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 13:57 r0ller
2013-01-10 14:25 ` 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=160aed40-5e04-41e2-ba4c-f78b8b270f24@googlegroups.com \
--to=r0ller@freemail.hu \
--cc=berenger@riken.jp \
--cc=caml-list@inria.fr \
--cc=fa.caml@googlegroups.com \
--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