From: Joel Reymont <joelr1@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Google summer of Code proposal
Date: Sat, 21 Mar 2009 20:43:01 +0000 [thread overview]
Message-ID: <61A6655E-FD4E-45F8-AD7E-6050C2E0DDE5@gmail.com> (raw)
In-Reply-To: <200903211338.32805.jon@ffconsultancy.com>
On Mar 21, 2009, at 1:38 PM, Jon Harrop wrote:
> . You will succumb to ocamlopt's current run-time representation
> which is
> objectively inefficient (e.g. boxing floats, tuples, records) and
> was only
> chosen because the compiler lacks capabilities that LLVM already
> provides for
> you (primarily JIT compilation).
This is probably a stupid suggestion but why not have OCaml directly
generate machine code, without the use of assembler and linker?
Wouldn't this be easier than trying to couple OCaml with LLVM?
Separately, it's sort of funny that LLVM and its users are going
through all the trouble now, when Lisp and Forth have had runtime
compilation for years and years.
---
http://linkedin.com/in/joelreymont
next prev parent reply other threads:[~2009-03-21 20:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 12:39 Andrey Riabushenko
2009-03-21 13:01 ` [Caml-list] " Seo Sanghyeon
2009-03-21 13:47 ` Andrey Riabushenko
2009-03-21 14:51 ` Jon Harrop
2009-03-21 20:49 ` Joel Reymont
2009-03-21 21:35 ` Jon Harrop
2009-03-21 13:38 ` Jon Harrop
2009-03-21 20:43 ` Joel Reymont [this message]
2009-03-21 21:28 ` Michael Ekstrand
2009-03-23 17:23 ` [Caml-list] " Kuba Ober
2009-03-21 22:21 ` [Caml-list] " Jon Harrop
2009-03-22 0:12 ` Fermin Reig
2009-03-23 14:19 ` Xavier Leroy
2009-03-23 19:38 ` Jon Harrop
2009-03-24 15:39 ` Xavier Leroy
2009-03-30 15:42 ` Nicolas Cannasse
2009-03-30 15:56 ` Joel Reymont
2009-03-30 21:21 ` Jon Harrop
2009-03-31 0:36 ` Jon Harrop
[not found] <20090321204943.E2ACCBBFA@yquem.inria.fr>
2009-03-21 21:45 ` Andrey Riabushenko
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=61A6655E-FD4E-45F8-AD7E-6050C2E0DDE5@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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).