caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vitaly Lugovsky <vsl@ontil.ihep.su>
To: Alex Baretta <alex@baretta.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: Ocaml VM and bytecode
Date: Tue, 30 Jan 2001 15:06:17 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.10.10101301504330.1968-100000@ontil.ihep.su> (raw)
In-Reply-To: <002201c086a1$f96b7680$68aa6ed4@alex>

On Thu, 25 Jan 2001, Alex Baretta wrote:

> One more thing: is there a bytecode to binary compiler for Ocaml?

 I just trying to write this compiler (for Alpha and Sparc
architectures), but there is a lot of problems with branching...

 May be, somebody wants to join me in this project?

--

   V.S.Lugovsky aka Mauhuur (http://ontil.ihep.su/~vsl) (UIN=45482254)




  reply	other threads:[~2001-01-31 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25  7:39 Alex Baretta
2001-01-30 12:06 ` Vitaly Lugovsky [this message]
2001-01-31 12:50 Fabrice Le Fessant

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=Pine.LNX.4.10.10101301504330.1968-100000@ontil.ihep.su \
    --to=vsl@ontil.ihep.su \
    --cc=alex@baretta.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).