[Interpreter] Adds implementation of bytecode graph builder for LoadICSloppy/Strict

src/compiler/pipeline.cc

Index: src/compiler/pipeline.cc
diff --git a/src/compiler/pipeline.cc b/src/compiler/pipeline.cc
index 86b5ae5fa5ddea2a7f581ee771d4c7da854b54f4..128193ea1a47ee03404ea50ce08cdc6f9c79be10 100644
--- a/src/compiler/pipeline.cc
+++ b/src/compiler/pipeline.cc
@@ -1061,7 +1061,8 @@ Handle<Code> Pipeline::GenerateCode() {
 
   data.source_positions()->AddDecorator();
 
-  if (FLAG_loop_assignment_analysis) {
+  if (FLAG_loop_assignment_analysis &&
+      !data.info()->shared_info()->HasBytecodeArray()) {

[mythria, 2015/11/04 12:19:14]

If this phase is required, I think we have to add a similar one from bytecode.
For now I just disabled it, when we are building the graph from bytecode array.
I did not check where LoopAssignmentAnalsysis is used. This analysis crashes if
we enable it when we are building it from bytecode. I think it is because it
expects a AStGraph.

[rmcilroy, 2015/11/04 14:27:37]

Could you dig into this a bit more and figure out what it needs - it is probably
just that we aren't doing something we need to do in BytecodeGraphTester.

     Run<LoopAssignmentAnalysisPhase>();
   }