From: "Christopher L Conway" <cconway@cs.nyu.edu>
To: "Joel Reymont" <joelr1@gmail.com>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Which function is consing?
Date: Wed, 4 Jul 2007 10:12:38 -0400 [thread overview]
Message-ID: <4a051d930707040712y5ef0a861x2e0c5297e1e20c99@mail.gmail.com> (raw)
In-Reply-To: <90BAEAF7-0710-44A3-BB2C-5075A2619371@gmail.com>
Joel,
I'm not sure I understand you correctly, but it's highly doubtful that
consing is the hotspot in your program. If you're problem is
interpreting the mangled function names that show up in gprof, it's
sometimes possible to correlate execution count with source locations
using ocamlcp. See here:
http://procrastiblog.blogspot.com/2007/04/profiling-ocaml-revealed.html
This won't let you figure out "which function is consing" unless you
rename ::, e.g.,
let mycons x xs = x :: xs
Chris
On 7/4/07, Joel Reymont <joelr1@gmail.com> wrote:
> Folks,
>
> There's apparently no way to determine what function is consing using
> the profiler.
>
> How do you get around this limitation in your production code?
>
> Thanks, Joel
>
> --
> http://topdog.cc - EasyLanguage to C# compiler
> http://wagerlabs.com - Blog
>
>
>
>
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
next prev parent reply other threads:[~2007-07-04 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 10:52 Joel Reymont
2007-07-04 14:12 ` Christopher L Conway [this message]
2007-07-04 14:29 ` [Caml-list] " Jon Harrop
2007-07-04 14:29 ` Markus E.L.
2007-07-04 14:24 ` Joel Reymont
2007-07-04 14:45 ` Bünzli Daniel
2007-07-04 18:19 ` Jon Harrop
2007-07-04 16:05 ` Brian Hurt
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=4a051d930707040712y5ef0a861x2e0c5297e1e20c99@mail.gmail.com \
--to=cconway@cs.nyu.edu \
--cc=caml-list@yquem.inria.fr \
--cc=joelr1@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