From: Ville-Pertti Keinonen <will@exomi.com>
To: Jon Harrop <jon@jdh30.plus.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Memory allocation nano-benchmark.
Date: Wed, 16 Feb 2005 10:19:58 +0200 [thread overview]
Message-ID: <1108541998.669.22.camel@localhost> (raw)
In-Reply-To: <200502152051.55292.jon@jdh30.plus.com>
On Tue, 2005-02-15 at 20:51 +0000, Jon Harrop wrote:
> Indeed, I'm in the "remove -unsafe" camp. Even if OCaml only hoisted bounds
> checks in the simplest of cases, I think there would be a strong case for
> removing this option.
As far as I can tell OCaml *never* eliminates or hoists bounds checks
(or any other repetitive operation), even in the simplest of cases. It
does explicitly use unsafe operations in the standard library, though.
ocamlopt doesn't really perform a lot of optimizations. The most
significant ones (inlining, constant folding/value propagation, direct
calls) appear to be done in a single pass (asmcomp/closure.ml).
next prev parent reply other threads:[~2005-02-16 8:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 15:15 Christian Szegedy
2005-02-10 14:47 ` [Caml-list] " Frédéric Gava
2005-02-10 15:19 ` skaller
2005-02-10 16:36 ` Frédéric Gava
2005-02-10 17:56 ` Frédéric Gava
2005-02-10 19:56 ` Christian Szegedy
2005-02-10 23:58 ` Frédéric Gava
2005-02-11 9:22 ` Frédéric Gava
2005-02-11 13:04 ` skaller
2005-02-11 13:33 ` skaller
2005-02-11 21:07 ` Oliver Bandel
2005-02-12 0:44 ` skaller
2005-02-15 14:17 ` Frédéric Gava
2005-02-15 19:19 ` Christian Szegedy
2005-02-15 20:51 ` Jon Harrop
2005-02-16 8:19 ` Ville-Pertti Keinonen [this message]
2005-02-16 9:54 ` Jon Harrop
2005-02-16 10:56 ` Ville-Pertti Keinonen
2005-02-11 0:55 ` skaller
2005-02-10 14:56 ` Jon Harrop
2005-02-10 15:32 ` Ville-Pertti Keinonen
2005-02-10 14:59 ` John Prevost
2005-02-10 16:50 ` Marwan Burelle
2005-02-10 19:20 ` Christian Szegedy
2005-02-10 19:40 ` Jon Harrop
2005-02-11 11:26 ` Oliver Bandel
2005-02-12 13:42 ` Christian Szegedy
2005-02-11 1:04 ` skaller
2005-02-11 11:28 ` Oliver Bandel
2005-02-12 0:01 ` Guillaume
2005-02-12 0:36 ` skaller
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=1108541998.669.22.camel@localhost \
--to=will@exomi.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@jdh30.plus.com \
/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).