From: "Stéphane Glondu" <steph@glondu.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlopt vs camlc, different behaviour - how to track down?
Date: Tue, 25 Jun 2013 07:45:50 +0200 [thread overview]
Message-ID: <51C92E8E.4040901@glondu.net> (raw)
In-Reply-To: <1372089559-sup-2177@nixos>
Le 24/06/2013 18:03, Marc Weber a écrit :
> I'd like to find out why a ocamlc complied application behaves
> differently than a ocamlopt compiled one.
There are no guarantees on the evaluation order for some constructions,
I have already experienced differences between ocamlc and ocamlopt.
Looking at the bug tracker, we can find some reports about it:
http://caml.inria.fr/mantis/view.php?id=2910
http://caml.inria.fr/mantis/view.php?id=4072
--
Stéphane
next prev parent reply other threads:[~2013-06-25 5:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 16:03 Marc Weber
2013-06-25 1:12 ` [Caml-list] " Marc Weber
2013-06-25 5:45 ` Stéphane Glondu [this message]
2013-06-28 23:54 ` Marc Weber
2013-06-29 7:31 ` Gabriel Scherer
2013-07-10 1:56 ` Marc Weber
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=51C92E8E.4040901@glondu.net \
--to=steph@glondu.net \
--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).