Use MemoryChunk-based allocation for deoptimization entry code
authordanno@chromium.org <danno@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 24 Jan 2013 15:14:33 +0000 (15:14 +0000)
committerdanno@chromium.org <danno@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 24 Jan 2013 15:14:33 +0000 (15:14 +0000)
commitde17ce7701045f1d96a8c263023cfb52f638a936
tree6fda41c6b980f5b51ad59e4ab64aeb5485af47b3
parent3c523437389b8c956edf7fb4745901640b437f52
Use MemoryChunk-based allocation for deoptimization entry code

This is done by first committing the deoptimization entry code with a minimal
area size (OS::CommitPageSize) and later using CommitArea to adjust the size.

Review URL: https://codereview.chromium.org/11566011
Patch from Haitao Feng <haitao.feng@intel.com>.

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13494 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/deoptimizer.cc
src/deoptimizer.h
src/isolate.h
src/spaces.cc
src/spaces.h
test/cctest/test-alloc.cc
test/cctest/test-spaces.cc