Re-enable EnsureAllocationSiteDependentCodesProcessed.

The problem was that we don't use crankshaft on non-sse2 builds.
(on ARM non-vfp3).

R=danno@chromium.org

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

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

diff --git a/test/cctest/cctest.status b/test/cctest/cctest.status
index d73399f..ad7ee91 100644 (file)
--- a/test/cctest/cctest.status
+++ b/test/cctest/cctest.status
@@ -30,9 +30,6 @@
   # All tests prefixed with 'Bug' are expected to fail.
   'test-api/Bug*': [FAIL],
 
-  # TODO(mvstanton): reenable when I figure out why it fails on no-sse2 builds
-  'test-heap/EnsureAllocationSiteDependentCodesProcessed': [SKIP],
-
   ##############################################################################
   # BUG(382): Weird test. Can't guarantee that it never times out.
   'test-api/ApplyInterruption': [PASS, TIMEOUT],

diff --git a/test/cctest/test-heap.cc b/test/cctest/test-heap.cc
index 448c589..29533d4 100644 (file)
--- a/test/cctest/test-heap.cc
+++ b/test/cctest/test-heap.cc
@@ -3570,6 +3570,8 @@ TEST(EnsureAllocationSiteDependentCodesProcessed) {
   v8::internal::Heap* heap = CcTest::heap();
   GlobalHandles* global_handles = isolate->global_handles();
 
+  if (!isolate->use_crankshaft()) return;
+
   // The allocation site at the head of the list is ours.
   Handle<AllocationSite> site;
   {