Re: [Caml-list] enhancements for "perf" on OCaml code

["Maxime Dénès" <Maxime.Denes@inria.fr>]

Hello,

Is it related to the recently introduced "-with-frame-pointers" 
configure flag http://caml.inria.fr/mantis/view.php?id=5721 ?

The purpose of this flag seemed to be the use of the same perf tool.

Maxime.

On 12/07/2013 15:46, Mark Shinwell wrote:
> Linux has a tool called "perf" that enables the display of source code
> alongside time profiling information and the corresponding assembly code.
> (See https://perf.wiki.kernel.org/index.php/Tutorial, "perf annotate").
>
> I am pleased to announce an alpha version of the OCaml native code compiler
> that permits perf to do the same for OCaml code.  This compiler works only on
> x86-64 Linux, although porting it to other Linux targets should be
> straightforward.
>
> The compiler is available in OPAM.  If you add the remote repository
> git://github.com/mshinwell/opam-repo-dev then you should be able to
> "opam switch" to the 4.01-perf-annotate compiler.  Please let me have any
> reports of problems.
>
> After compilation, you can run "perf record" to gather data about your
> OCaml program, and then use "perf report" to interactively examine it.
> If you hit Return on a function, then you should be given the option to
> annotate it, and then you should see the OCaml code as above.  Note that
> line number information is not yet as fine-grained for OCaml as it might
> be for C code.
>
> You need to have the source files available at the same location on the
> filesystem when you run "perf report" as you did when you compiled the
> program.
>
> This work forms part of a larger project in collaboration with OCaml Labs
> at Cambridge, UK, to enhance the level of debugging information emitted
> by the OCaml compiler.  The perf-annotate compiler emits debugging sections
> that aim to be compliant with the DWARF-2 standard.
>
> Mark
>
> P.S. The eagle-eyed of you will notice that there is another compiler,
> 4.01-allocation-profiling, also available in that OPAM repo.  This provides
> allocation profiling capabilities for native code, documentation for which I
> will endeavour to circulate to the list shortly.
>