Because allocation in large object space can now require checking the
authorkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 29 Oct 2008 10:00:38 +0000 (10:00 +0000)
committerkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 29 Oct 2008 10:00:38 +0000 (10:00 +0000)
size of the entire old generation, the heap must be (more) properly
set up to test the large object space.
Review URL: http://codereview.chromium.org/8872

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@634 ce2b1a6d-e550-0410-aec6-3dcde31c8c00

test/cctest/test-spaces.cc

index 86aa5f88a7bcfb26df81e546b36ab1b2041c4cda..d946a7fa5449e90b16a470bc5d2ce7a977a16b5c 100644 (file)
@@ -207,14 +207,11 @@ TEST(OldSpace) {
 
 
 TEST(LargeObjectSpace) {
-  CHECK(Heap::ConfigureHeapDefault());
-  MemoryAllocator::Setup(Heap::MaxCapacity());
+  CHECK(Heap::Setup(false));
 
-  LargeObjectSpace* lo = new LargeObjectSpace(LO_SPACE);
+  LargeObjectSpace* lo = Heap::lo_space();
   CHECK(lo != NULL);
 
-  CHECK(lo->Setup());
-
   Map* faked_map = reinterpret_cast<Map*>(HeapObject::FromAddress(0));
   int lo_size = Page::kPageSize;