Reviewers: Vitaly,
Description:
The object's space in Page starts after Page header and is aligned to
kMapAlignment which is 32 bytes on 32-bit and 8 bytes on 64-bit.
In case of 64-bit target, the current page header size is exactly 32 bytes
so we
get the code magically aligned at 32 bytes but it is better to have a
separate
CODE_POINTER_ALIGN macro to make sure the object space in Page is aligned
properly for both maps and code.
There could be a small waste of bytes sometimes (since both Page header and
Code
header sizes are aligned separately) but it seems the optimal one would
involve
cross-dependencies between .h files and not clear if it's worth it.
This is a back-port from Isolates branch.
Please review this at http://codereview.chromium.org/3461021/show
Affected files:
M src/globals.h
M src/heap.cc
M src/objects-debug.cc
M src/objects.h
M src/spaces.h
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
