From: Dave Mason <dmason@sarg.ryerson.ca>
To: caml-list@inria.fr
Cc: Chris Hecker <checker@d6.com>,
Markus Mottl <markus@mail4.ai.univie.ac.at>,
Jerome Vouillon <vouillon@saul.cis.upenn.edu>
Subject: Re: [Caml-list] calling native from bytecode
Date: Tue, 25 Sep 2001 18:40:49 -0400 [thread overview]
Message-ID: <200109252240.f8PMenf08237@sarg.ryerson.ca> (raw)
In-Reply-To: Your message of "Tue, 25 Sep 2001 14:22:09 PDT." <4.3.2.7.2.20010925141543.02a904f0@arda.pair.com>
>>>>> On Tue, 25 Sep 2001 14:22:09 -0700, Chris Hecker <checker@d6.com> said:
> I was going to reply to that same quote and reiterate my desire to
> link native and bytecode! :)
I hate me-too mailings on lists, but... :-)
I honestly think this is one of the most important issues with ocaml
at the moment. The native code compiler is good enough that we
frequently see examples of it beating C code (sometimes partly because
of having to jump the barrier between ocaml and C, but still...). It
is a huge shame that we can't use the resulting code in the
interpreter.
I wonder how much of the runtime library would be speeded up (and made
more robust) if it were coded in ocaml instead of C.
Please, please, please!
Unfortunately, I don't have the time right now, or a grad student with
the aptitude, or I'd do it. It would be *very* cool to have ocaml all
the way down to the metal!
../Dave
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-09-26 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 17:12 [Caml-list] RE: a regular expression library Jerome Vouillon
2001-09-25 18:40 ` Miles Egan
2001-09-25 19:03 ` Markus Mottl
2001-09-25 21:22 ` [Caml-list] calling native from bytecode (was RE: a regular expression library) Chris Hecker
2001-09-25 22:40 ` Dave Mason [this message]
2001-11-09 15:09 ` [Caml-list] avoiding native call from bytecode issue via dynamic linking Jeff Henrikson
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=200109252240.f8PMenf08237@sarg.ryerson.ca \
--to=dmason@sarg.ryerson.ca \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
--cc=markus@mail4.ai.univie.ac.at \
--cc=vouillon@saul.cis.upenn.edu \
/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).