Enable incremental code flushing.

src/heap.cc

Index: src/heap.cc
diff --git a/src/heap.cc b/src/heap.cc
index 5de06aa607e76438bb795ceb8507f272714cf943..76ab573e82d0048691f14b4a06ffa6fda813d4e0 100644
--- a/src/heap.cc
+++ b/src/heap.cc
@@ -406,6 +406,14 @@ void Heap::GarbageCollectionPrologue() {
   gc_count_++;
   unflattened_strings_length_ = 0;
 
+  bool should_enable_code_flushing = FLAG_flush_code;
+#ifdef ENABLE_DEBUGGER_SUPPORT
+  if (isolate_->debug()->IsLoaded() || isolate_->debug()->has_break_points()) {

[ulan, 2012/10/16 08:09:31]

What if this condition becomes true during incremental marking after we enabled
code flushing? Will it break the debugger?

[Michael Starzinger, 2012/10/16 08:27:54]

When the condition becomes true, the debugger will trigger a GC with
kMakeHeapIterable, which imples kAbortIncrementalMarking. So it's implicitly
aborted. But you are right, this requires a comment either here or in the
debugger. Will add the comment.

+    should_enable_code_flushing = false;
+  }
+#endif
+  mark_compact_collector()->EnableCodeFlushing(should_enable_code_flushing);
+
 #ifdef VERIFY_HEAP
   if (FLAG_verify_heap) {
     Verify();