On 2013/10/23 10:51:02, Hannes Payer wrote:
So the problem is that the map pointer is not set in the newly allocated
object.
Why don't we install a free space filler with the appropriate size there
after
allocating but right before reporting? This should solve the problem and
does
not spread the reporting code all over the heap allocation functions.
WDYT?
That was another option we considered but Ilya argued against that approach
as
it would increase complexity of the code. Also we would probably have to do
similar work in the generated code. I like the current approach slightly
better
as it doesn't require modifying the current allocation logic except
reporting
allocations in appropriate places. Ilya what do you think?
https://codereview.chromium.org/34733004/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
