From: David Baelde <david.baelde@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] documentation on ocamlopt backend
Date: Sat, 10 Dec 2005 15:23:50 +0100 [thread overview]
Message-ID: <53c655920512100623l82ffd88g@mail.gmail.com> (raw)
In-Reply-To: <E6A6245C-39C9-4D4C-8D3E-6C29B96127FB@cs.stanford.edu>
2005/12/10, Ted Kremenek <kremenek@cs.stanford.edu>:
> I'm potentially interested in writing a new backend target for
> ocamlopt. I looked around in the Ocaml distribution subdirectory
> "asmcomp" (which is where the target-specific portion of the backend
> appears to be implemented), but there is not very much documentation
> there. In particular, I'm interested in generating assembly that
> will be piped through an assembler that is not "as."
I back this kind of request! I would be very interesting in re-using
parts of the compiler, and I believe many people would like to re-use
or change several parts of OCaml compiler. It would be great to have
somebody with a decent knowledge of the compiler put it down. Maybe
somebody did it already ?
--
David
prev parent reply other threads:[~2005-12-10 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 1:57 Ted Kremenek
2005-12-10 14:23 ` David Baelde [this message]
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=53c655920512100623l82ffd88g@mail.gmail.com \
--to=david.baelde@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=david.baelde@ens-lyon.org \
/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).