caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Arthur Chan" <baguasquirrel@gmail.com>
To: "Jake Donham" <jake@donham.org>
Cc: "Raj Bandyopadhyay" <rajb@rice.edu>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Q: Profiling ocaml using gprof
Date: Mon, 14 Jul 2008 22:42:39 -0700	[thread overview]
Message-ID: <74cabd9e0807142242n3854dcf7w6d0cfacb0ca6d6a3@mail.gmail.com> (raw)
In-Reply-To: <c7e4e9f0807142109q212f2f11o779156fab31a7a93@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

Is gprof better for profiling ocaml than ocaml's own profilers?

How would you go about figuring out that that particular function stub is
string concat?


On Mon, Jul 14, 2008 at 9:09 PM, Jake Donham <jake@donham.org> wrote:

>  On Mon, Jul 14, 2008 at 6:52 PM, Raj Bandyopadhyay <rajb@rice.edu> wrote:
> > 'camlPervasives__$5e_136'.
>
> It's the string concatenation function (ASCII 5E is ^).
>
> It allocates a new string and blits the two argument strings into it,
> so you can probably do much better with explicit use of the Buffer
> module.
>
> Jake
>
> _______________________________________________
> 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
>



-- 
-----------------------------------------------------------------------
(\__/)
(='.'=)This is Bunny. Copy and paste Bunny into your
(")_(")signature to help him gain world domination.
------------------------------------------------------------------------

[-- Attachment #2: Type: text/html, Size: 1887 bytes --]

  reply	other threads:[~2008-07-15  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  1:52 Raj Bandyopadhyay
2008-07-15  4:09 ` [Caml-list] " Jake Donham
2008-07-15  5:42   ` Arthur Chan [this message]
2008-07-15  9:12     ` Richard Jones
2008-07-15  7:11   ` Vincent Hanquez

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=74cabd9e0807142242n3854dcf7w6d0cfacb0ca6d6a3@mail.gmail.com \
    --to=baguasquirrel@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jake@donham.org \
    --cc=rajb@rice.edu \
    /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;
as well as URLs for NNTP newsgroup(s).