[turbofan] Enable BytecodeGraphBuilder by default.

test/cctest/compiler/function-tester.cc

Index: test/cctest/compiler/function-tester.cc
diff --git a/test/cctest/compiler/function-tester.cc b/test/cctest/compiler/function-tester.cc
index 2da2dc14aa3597adb03d93f14074b6519a8d7836..4d7ed383c0f44e9874b8306eaa9a2f44d65431ae 100644
--- a/test/cctest/compiler/function-tester.cc
+++ b/test/cctest/compiler/function-tester.cc
@@ -161,23 +161,19 @@ Handle<JSFunction> FunctionTester::Compile(Handle<JSFunction> function) {
   Zone zone(function->GetIsolate()->allocator());
   ParseInfo parse_info(&zone, function);
   CompilationInfo info(&parse_info, function);
-  info.MarkAsDeoptimizationEnabled();
 
-  if (!FLAG_turbo_from_bytecode) {
-    CHECK(Parser::ParseStatic(info.parse_info()));
-  }
   info.SetOptimizing();
+  info.MarkAsDeoptimizationEnabled();
   if (flags_ & CompilationInfo::kNativeContextSpecializing) {
     info.MarkAsNativeContextSpecializing();
   }
   if (flags_ & CompilationInfo::kInliningEnabled) {
     info.MarkAsInliningEnabled();
   }
-  if (FLAG_turbo_from_bytecode) {
-    CHECK(Compiler::EnsureBytecode(&info));
+  if (Compiler::EnsureBytecode(&info)) {

[rmcilroy, 2016/10/06 14:22:57]

Just thinking about this again - this basically makes it impossible to use the
ASTGraphBuilder even when turbo_from_bytecode is false, right? This means we
can't do (local) experiments comparing graphs built with ASTGraphBuilder and
BytecodeGraphBuilder. Should we allow that ability until we've got rid of all
the regressions between BCGB and ASTGraphBuilder? 

[Michael Starzinger, 2016/10/06 14:26:12]

This is true for cctest, yes. But compiler.cc still has support for
--noturbo-from-bytecode for (local) experimentation via the d8 shell.

     info.MarkAsOptimizeFromBytecode();
   } else {
-    CHECK(Compiler::Analyze(info.parse_info()));
+    CHECK(Compiler::ParseAndAnalyze(info.parse_info()));
     CHECK(Compiler::EnsureDeoptimizationSupport(&info));
   }
   JSFunction::EnsureLiterals(function);