[compiler] Add baseline tier to compilation pipeline.

src/objects.cc

Index: src/objects.cc
diff --git a/src/objects.cc b/src/objects.cc
index 202fb5ce9ffaf3c5ed3a17a6a5da22850152e168..5dd204b56f09187665293e30e55532e6f0aa3b00 100644
--- a/src/objects.cc
+++ b/src/objects.cc
@@ -11970,6 +11970,12 @@ bool JSFunction::Inlines(SharedFunctionInfo* candidate) {
   return false;
 }
 
+void JSFunction::MarkForBaseline() {
+  Isolate* isolate = GetIsolate();
+  set_code_no_write_barrier(
+      isolate->builtins()->builtin(Builtins::kCompileBaseline));

[rmcilroy, 2016/04/22 10:02:57]

Should we have a flag --no-baseline or --no-full-codegen or similar (like
--no-crankshaft) so we can disable baseline compilation. (The check should
probably live in compiler.cc, not here though).

[Michael Starzinger, 2016/04/22 10:47:45]

Acknowledged. Yes, totally agree. I also want to add a --always-baseline (or
similarly named) flag that stressed tiering up to baseline code. I plan to add
this in a follow-up CL. And yes, I agree, the check for this flag should live in
compiler.cc (or the runtime profiler), definitely not here.

+  // No write barrier required, since the builtin is part of the root set.
+}
 
 void JSFunction::MarkForOptimization() {
   Isolate* isolate = GetIsolate();