The goal is to discover the appropriate heap space for objects created in full
authormvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 27 Nov 2013 14:03:40 +0000 (14:03 +0000)
committermvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 27 Nov 2013 14:03:40 +0000 (14:03 +0000)
commitf3a22f965ef8ccf6ab9c94ea2b20b206ef7406bd
tree4da5c3cf59350839910a1660db79d35b82db7e54
parent50a4bb508483d5998bc65b2ef1f9de026394c89e
The goal is to discover the appropriate heap space for objects created in full
code. By the time we optimize the code, we'll be able to decide on new or old
space based on the number of surviving objects after one or more gcs.

The mechanism is a "memento" placed behind objects in the heap. It's currently
done for array and object literals, with plans to use mementos for constructed
objects as well (in a later CL).

The feature is behind the flag allocation_site_pretenuring, currently off.

R=hpayer@chromium.org

Review URL: https://codereview.chromium.org/40063002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18104 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
17 files changed:
src/allocation-site-scopes.cc
src/allocation-site-scopes.h
src/arm/full-codegen-arm.cc
src/heap-inl.h
src/heap.cc
src/heap.h
src/hydrogen.cc
src/hydrogen.h
src/ia32/full-codegen-ia32.cc
src/mark-compact.cc
src/mark-compact.h
src/mips/full-codegen-mips.cc
src/objects-inl.h
src/objects.cc
src/objects.h
src/x64/full-codegen-x64.cc
test/cctest/test-heap.cc