From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] time profiling and nested function inlining
Date: Thu, 7 Dec 2006 12:14:29 +0000 [thread overview]
Message-ID: <200612071214.29263.jon@ffconsultancy.com> (raw)
In-Reply-To: <8E63D477-08E0-485C-A250-6E90A699A253@lrde.epita.fr>
On Thursday 07 December 2006 10:43, Quôc Peyrot wrote:
> in the former, the compiler doesn't detect the invariant "array.(i)"
> and keeps it inside the inner loop.
> I tried to pass -ccopt -O3 to ocamlopt but it didn't seem to change
> anything.
Ocamlopt doesn't do that optimisation and -ccopt won't have any effect unless
you're compiling C code.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
prev parent reply other threads:[~2006-12-07 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 3:43 Quôc Peyrot
2006-12-06 8:55 ` [Caml-list] " Daniel Bünzli
2006-12-06 9:01 ` Daniel Bünzli
2006-12-07 10:43 ` Quôc Peyrot
2006-12-07 12:14 ` Jon Harrop [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=200612071214.29263.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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).