From: Jeffrey Mathews <jnamathews@acm.org>
To: caml-list@inria.fr
Subject: Floating point optimization patch for OCaml bytecode
Date: Thu, 15 Sep 2005 19:21:21 -0400 [thread overview]
Message-ID: <305c47f0509151621621a630d@mail.gmail.com> (raw)
I know, I know -- why bother optimizing bytecode? (Compelling reasons
have long been debated -- for me, it's a need to do dynamic- / meta-
programming.)
Anyway, I've written a small patch for the OCaml bytecode compiler and
runtime that significantly improves the performance of a few
floating-point intensive benchmarks (from 30 to 40%) by reducing
boxing and unboxing of intermediate floating point results.
This is still preliminary work, and honestly I'm a little suspicious
that it works so well. Testing has also been light -- it compiles and
runs my 'benchmark' script when patched against ocaml 3.08.1 and
3.08.4 (as well as MetaOcaml, though the patch needs a little
coaxing).
A short write-up can be found at http://dem.inim.us/ocamlfp/README-FP.html
The patch is found at http://dem.inim.us/ocamlfp/ocamlfp-0.1.diff.gz
I'd greatly appreciate feedback, criticism, testing on other platforms.
Thanks in advance,
Jeff
next reply other threads:[~2005-09-15 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 23:21 Jeffrey Mathews [this message]
2005-09-16 15:17 ` [Caml-list] " Damien Guichard
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=305c47f0509151621621a630d@mail.gmail.com \
--to=jnamathews@acm.org \
--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).