From: "Mark Shinwell" <mshinwell@janestcapital.com>
To: Alexey Rodriguez <mrchebas@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlopt debugging options
Date: Thu, 23 Apr 2009 11:34:30 +0100 [thread overview]
Message-ID: <20090423103430.GH29676@janestcapital.com> (raw)
In-Reply-To: <4b39c80a0904230330r759d3429jae4146d2c2db7a36@mail.gmail.com>
On Thu, Apr 23, 2009 at 12:30:31PM +0200, Alexey Rodriguez wrote:
> Sometimes it is useful to see what is the code produced by ocamlopt in
> order to assess the performance of programming constructs. It is
> possible to use -dcmm, but it is difficult to relate ocaml functions
> to their compiled form due to the names used in the cmm dump. How do
> you people get around that difficulty?
I use objdump -Dr :)
Mark
next prev parent reply other threads:[~2009-04-23 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 10:30 Alexey Rodriguez
2009-04-23 10:34 ` Mark Shinwell [this message]
2009-06-18 13:52 ` [Caml-list] " Alexey Rodriguez
2009-06-18 13:57 ` Daniel Bünzli
2009-06-18 14:10 ` Alexey Rodriguez
2009-06-18 14:10 ` Mark Shinwell
2009-06-18 14:11 ` Alexey Rodriguez
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=20090423103430.GH29676@janestcapital.com \
--to=mshinwell@janestcapital.com \
--cc=caml-list@inria.fr \
--cc=mrchebas@gmail.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