[wasm] Generated the framework in wasm-module for parallel compilation.

src/compiler/wasm-compiler.h

Index: src/compiler/wasm-compiler.h
diff --git a/src/compiler/wasm-compiler.h b/src/compiler/wasm-compiler.h
index a27571f22b105b171b2c31cd83b2a5876c8967fa..a624b41dfaf5f9dfe10efa9ab55a94945ceecc02 100644
--- a/src/compiler/wasm-compiler.h
+++ b/src/compiler/wasm-compiler.h
@@ -20,6 +20,7 @@ class JSGraph;
 class Graph;
 class Operator;
 class SourcePositionTable;
+class WasmCompilationUnit;
 }
 
 namespace wasm {
@@ -35,9 +36,9 @@ typedef compiler::JSGraph TFGraph;
 
 namespace compiler {
 // Compiles a single function, producing a code object.
-Handle<Code> CompileWasmFunction(wasm::ErrorThrower& thrower, Isolate* isolate,
+Handle<Code> CompileWasmFunction(wasm::ErrorThrower* thrower, Isolate* isolate,
                                  wasm::ModuleEnv* module_env,
-                                 const wasm::WasmFunction& function);
+                                 const wasm::WasmFunction* function);
 
 // Wraps a JS function, producing a code object that can be called from WASM.
 Handle<Code> CompileWasmToJSWrapper(Isolate* isolate, wasm::ModuleEnv* module,
@@ -52,6 +53,16 @@ Handle<JSFunction> CompileJSToWasmWrapper(
     Isolate* isolate, wasm::ModuleEnv* module, Handle<String> name,
     Handle<Code> wasm_code, Handle<JSObject> module_object, uint32_t index);
 
+WasmCompilationUnit* CreateWasmCompilationUnit(

[titzer, 2016/04/28 13:09:47]

We will probably want to group multiple adjacent functions into the same
compilation unit (especially when there are thousands of tiny functions). So the
design of the WasmCompilationUnit should probably support multiple functions.

[ahaas, 2016/04/28 14:56:31]

My plan was that a background task fetches several WasmCompilationUnits at a
time and then processes them. Thereby we get a good load balancing without
introducing to much contention on the working queue.

Aside from that the plan is that a WasmCompilationUnit contains all data needed
to compile a single function. If we want to create work packages which contain
multiple functions, then I would create another class for that. Should I rename
this class to make its purpose more obvious?

+    wasm::ErrorThrower* thrower, Isolate* isolate, wasm::ModuleEnv* module_env,
+    const wasm::WasmFunction* function);
+
+void ExecuteCompilation(WasmCompilationUnit* unit);
+
+int GetIndexOfWasmCompilationUnit(WasmCompilationUnit* unit);
+
+Handle<Code> FinishCompilation(WasmCompilationUnit* unit);
+
 // Abstracts details of building TurboFan graph nodes for WASM to separate
 // the WASM decoder from the internal details of TurboFan.
 class WasmTrapHelper;