From: Damien Doligez <damien.doligez@inria.fr>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Specifying ocamlprof.dump output filename
Date: Tue, 28 Nov 2006 16:27:53 +0100 [thread overview]
Message-ID: <090FAEF8-24FA-4144-A342-D35C73061322@inria.fr> (raw)
In-Reply-To: <700d600f0611120115v77c2b9ebh76b94791fb24a05b@mail.gmail.com>
On 2006-11-12, at 10:15, Janne Hellsten wrote:
> 1. Profiling results are not accumulated across all of the separate
> testers. Each test directory produce a separate results file, and
> I need to go through these results one by one. I'd like to only
> get the combined results:
>
> $PROJ/test/size/ocamlprof.dump
> $PROJ/test/speed/ocamlprof.dump
> $PROJ/test/func/ocamlprof.dump
>
> =>
>
> $PROJ/bin/ocamlprof.dump # combined result
You can solve this one by setting up symbolic links before profiling
your program.
> 2. Running other bytecode programs compiled for profiling resets the
> dump files. I run several OCamlprof-enabled programs in my
> regression suite. As all of these are run in the same working
> directory, these programs end up overwriting each others results.
You can solve this one by copying or renaming the dump files
between the runs of your programs. I agree this is inconvenient.
> Would it make sense to add a command line option for ocamlcp that
> would override the default ocamlprof.dump output path?
Not really. What to do when two source files are compiled
with different values for this option?
What I will implement is an environment variable, to specify
the name of the dump file used when profiling. Then you just
have to set it before running your programs.
-- Damien
prev parent reply other threads:[~2006-11-28 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 9:15 Janne Hellsten
2006-11-28 15:27 ` Damien Doligez [this message]
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=090FAEF8-24FA-4144-A342-D35C73061322@inria.fr \
--to=damien.doligez@inria.fr \
--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