From: Raj B <rajb@rice.edu>
To: caml-list@yquem.inria.fr
Subject: Native compiler optimizations
Date: Wed, 6 Jun 2007 11:13:50 -0500 [thread overview]
Message-ID: <79BFC310-5500-40EE-97A5-88FA56C643B2@rice.edu> (raw)
Hi
This is a fairly broad question, but I do need as much info as I can
get. I'm trying to understand
how the OCaml native code compiler works in order to improve my
application's performance.
What kind of compiler optimizations are performed by the OCaml native
code compiler? In particular, what does it do in case of imperative
features (loop, references, sequences). Are there common compiler
optimizations that it does not do, especially compared to C or Fortran?
('Optimizations', of course, is a very broad term)
I've also read somewhere that OCaml optimizes tail-recursion. Does
that mean I don't need to write
for/while-loops if I don't want to without worrying about
performance? Recursion does look cleaner :)
This is probably a much-discussed topic, and I have looked at some of
the older threads (2005 and older). However, I'd appreciate any new
information. The older threads talk about a few books in progress
discussing these issues.
If there's a specific section of the OCaml code base I should stare
at, I'd be glad to know too.
Thanks
Raj
reply other threads:[~2007-06-06 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=79BFC310-5500-40EE-97A5-88FA56C643B2@rice.edu \
--to=rajb@rice.edu \
--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