Move new-space allocation tracking into Heap::AllocateRaw.

Move new-space allocation tracking into Heap::AllocateRaw.

R=yurys@chromium.org

Committed: http://code.google.com/p/v8/source/detail?r=17605

[Michael Starzinger, 2013-11-08 14:44:48]

By now all allocations in new-space done by the runtime (not the generated code)
go through Heap::AllocateRaw. This CL moves the allocation tracking into the
same choke-point.

The same should be done for old-space as well, once the three remaining
call-sites in Heap::CreateCode and Heap::CopyCode are taken care of.

Let me know if I missed any call-sites that the heap profiler was tracking
before but is not tracking now. Also note that this CL depends on
https://codereview.chromium.org/66723003/ to be landed first.

[yurys, 2013-11-08 16:05:19]

LGTM!

On 2013/11/08 14:44:48, Michael Starzinger wrote:
> By now all allocations in new-space done by the runtime (not the generated
code)
> go through Heap::AllocateRaw. This CL moves the allocation tracking into the
> same choke-point.
> 
> The same should be done for old-space as well, once the three remaining
> call-sites in Heap::CreateCode and Heap::CopyCode are taken care of.
> 
Yeah, we discussed this with Hannes here:
https://codereview.chromium.org/34733004#msg10 Spaces shouldn't be aware of
HeapProfiler, all hooks should ideally be in Heap.

> Let me know if I missed any call-sites that the heap profiler was tracking
> before but is not tracking now. Also note that this CL depends on
> https://codereview.chromium.org/66723003/ to be landed first.

[Michael Starzinger, 2013-11-08 17:23:33]

Committed patchset #1 manually as r17605 (presubmit successful).