From: "Dominique Martinet" <asmadeus77@gmail.com>
To: "Richard Jones" <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml image blending performance
Date: Thu, 7 Feb 2008 12:13:39 +0100 [thread overview]
Message-ID: <b79ece760802070313i49436350h2cbe7f61617edc2b@mail.gmail.com> (raw)
In-Reply-To: <20080207110154.GA24561@annexia.org>
I haven't looked at the code nor the build options, but you might want
to try the unsafe get and set functions if you did your own bundary
checks before, instead of having caml check it everytime it access
some data.
It saved us roughtly 20% of running time on a project involving ALOT
of array accesses
next prev parent reply other threads:[~2008-02-07 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 20:29 Ilmari Heikkinen
2008-02-06 22:12 ` [Caml-list] " Pal-Kristian Engstad
2008-02-06 23:30 ` Jon Harrop
2008-02-06 23:34 ` Jon Harrop
2008-02-07 11:01 ` Richard Jones
2008-02-07 11:13 ` Dominique Martinet [this message]
2008-02-07 12:29 ` Mauricio Fernandez
2008-02-07 15:04 ` Jon Harrop
[not found] ` <854c25eb0802070607t4b2ed641xa3bc19e8384ce23@mail.gmail.com>
2008-02-07 14:10 ` Ilmari Heikkinen
2008-02-07 14:08 ` Jon Harrop
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=b79ece760802070313i49436350h2cbe7f61617edc2b@mail.gmail.com \
--to=asmadeus77@gmail.com \
--cc=caml-list@inria.fr \
--cc=rich@annexia.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).