From: Marc Weber <marco-oweber@gmx.de>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] ocamlopt vs camlc, different behaviour - how to track down?
Date: Mon, 24 Jun 2013 18:03:13 +0200 [thread overview]
Message-ID: <1372089559-sup-2177@nixos> (raw)
I'd like to find out why a ocamlc complied application behaves
differently than a ocamlopt compiled one.
Because "deriving show" for arbitrary data blocks is kind of hard
(it looks like derivig fails on parameterized types?) the next best
thing which comes to my mind is making each instruction trace its source
position. This way it should be easy to find out why ocamlopt result
behaves differently than ocamlc by diffing the traces.
Is there any starting point - such as a camlp4 post processor I could
use and adopt?
Marc Weber
next reply other threads:[~2013-06-24 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 16:03 Marc Weber [this message]
2013-06-25 1:12 ` [Caml-list] " Marc Weber
2013-06-25 5:45 ` [Caml-list] " Stéphane Glondu
2013-06-28 23:54 ` [Caml-list] " 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=1372089559-sup-2177@nixos \
--to=marco-oweber@gmx.de \
--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