Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1145)

Unified Diff: src/spaces.h

Issue 20867003: More cleanup regarding the maximum non-large object allocation size. (Closed) Base URL: https://v8.googlecode.com/svn/branches/bleeding_edge
Patch Set: Created 7 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « src/objects-visiting.h ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: src/spaces.h
diff --git a/src/spaces.h b/src/spaces.h
index b47452e421feeb5c61f8f083d908956eae99a046..63164057d7948f389e0ca4249b7d75c274e6ef5c 100644
--- a/src/spaces.h
+++ b/src/spaces.h
@@ -778,8 +778,9 @@ class Page : public MemoryChunk {
// Page size in bytes. This must be a multiple of the OS page size.
static const int kPageSize = 1 << kPageSizeBits;
- // Object area size in bytes.
- static const int kNonCodeObjectAreaSize = kPageSize - kObjectStartOffset;
+ // Object area size in bytes. Take double alignment into account.
+ static const int kNonCodeObjectAreaSize =
+ kPageSize - kObjectStartOffset - kPointerSize;
Michael Starzinger 2013/08/02 12:30:53 I don't think the wiggle room for double alignment
Hannes Payer (out of office) 2013/08/05 12:52:21 Done.
// Maximum object size that fits in a page. Objects larger than that size
// are allocated in large object space and are never moved in memory. This
« no previous file with comments | « src/objects-visiting.h ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698