Change the CompilationInfo::IsCodePreAgingActive() predicate to CompilationInfo::GeneratePreagingPr…

src/compiler.h

Index: src/compiler.h
diff --git a/src/compiler.h b/src/compiler.h
index c7b822293c1a8ae685fba6ad605fb1b44ef1d309..f802992815a3e998c31c237d2dac8b64868fd1a9 100644
--- a/src/compiler.h
+++ b/src/compiler.h
@@ -268,10 +268,11 @@ class CompilationInfo {
 
   bool is_first_compile() const { return GetFlag(kFirstCompile); }
 
-  bool IsCodePreAgingActive() const {
-    // TODO(bradnelson): Figure out why this breaks wasm.
+  bool GeneratePreagedPrologue() const {
+    // WASM functions cannot be aged, since they have no corresponding

[Michael Starzinger, 2016/01/12 09:43:34]

As discussed offline: Can we slightly rephrase the comment? Since the reason for
not pre-aging WASM functions is because it doesn't make sense to age/flush WASM
functions, and not that we technically couldn't age them.

+    // unoptimized code.
     return FLAG_optimize_for_size && FLAG_age_code && !will_serialize() &&
-           !is_debug() && !FLAG_expose_wasm;
+           !is_debug() && output_code_kind_ != Code::WASM_FUNCTION;
   }
 
   void EnsureFeedbackVector();