From: Mark Shinwell <mshinwell@janestreet.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Allocation profiling for x86-64 native code
Date: Mon, 16 Sep 2013 09:00:21 +0100 [thread overview]
Message-ID: <CAM3Ki74hS1UVmtLVX=95WJMK51nfuBsYnBwPiR+0xMAoDV6oLA@mail.gmail.com> (raw)
In-Reply-To: <1379091130.2471.12.camel@e130>
On 13 September 2013 17:52, Gerd Stolpmann <info@gerd-stolpmann.de> wrote:
> A dumb question: how do you do the value instrumentation? Without space
> overhead? There is not much information in the value itself...
The maximum size of blocks is reduced and then an
approximation to the instruction pointer at the point of
allocation is stored in the spare space in the header
word. (More detail to follow in a reply to Jacques-Henri.)
Mark
next prev parent reply other threads:[~2013-09-16 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:48 Mark Shinwell
2013-09-13 16:52 ` Gerd Stolpmann
2013-09-16 8:00 ` Mark Shinwell [this message]
2013-09-14 22:10 ` Jacques-Henri Jourdan
2013-09-16 8:42 ` Mark Shinwell
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='CAM3Ki74hS1UVmtLVX=95WJMK51nfuBsYnBwPiR+0xMAoDV6oLA@mail.gmail.com' \
--to=mshinwell@janestreet.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
/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).