The memory size test makes no sense on the simulated platforms.

Review URL: http://codereview.chromium.org/8818007

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

diff --git a/test/cctest/test-mark-compact.cc b/test/cctest/test-mark-compact.cc
index e4c885c656ce5e95748e7a4161e28e7fe215b251..3c66c4c80ba23b4b2180bd590aba4f2c93baf79b 100644 (file)
--- a/test/cctest/test-mark-compact.cc
+++ b/test/cctest/test-mark-compact.cc
@@ -454,7 +454,10 @@ TEST(EmptyObjectGroups) {
 }
 
 
-#ifdef __linux__
+// Here is a memory use test that uses /proc, and is therefore Linux-only.  We
+// do not care how much memory the simulator uses, since it is only there for
+// debugging purposes.
+#if defined(__linux__) && !defined(USE_SIMULATOR)
 
 
 static uintptr_t ReadLong(char* buffer, intptr_t* position, int base) {
@@ -532,4 +535,4 @@ TEST(BootUpMemoryUse) {
   }
 }
 
-#endif  // __linux__
+#endif  // __linux__ and !USE_SIMULATOR