Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(950)

Unified Diff: src/wasm/wasm-module.cc

Issue 2472103002: [wasm] Store the function_index in the js-to-wasm wrapper instead of the export index (Closed)
Patch Set: Store the function index in the wrapper instead. Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | test/mjsunit/wasm/test-import-export-wrapper.js » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: src/wasm/wasm-module.cc
diff --git a/src/wasm/wasm-module.cc b/src/wasm/wasm-module.cc
index aa385f824e6917b38815aadf8d047c4fa5964ea4..49107c86913ef2821d4d1717024a4a415426a591 100644
--- a/src/wasm/wasm-module.cc
+++ b/src/wasm/wasm-module.cc
@@ -1644,9 +1644,9 @@ class WasmInstanceBuilder {
// Wrap the exported code as a JSFunction.
Handle<Code> export_code =
code_table->GetValueChecked<Code>(isolate_, export_index);
- js_function =
- WrapExportCodeAsJSFunction(isolate_, export_code, name,
- function.sig, func_index, instance);
+ js_function = WrapExportCodeAsJSFunction(
+ isolate_, export_code, name, function.sig, function.func_index,
+ instance);
js_wrappers_[exp.index] = js_function;
}
desc.set_value(js_function);
« no previous file with comments | « no previous file | test/mjsunit/wasm/test-import-export-wrapper.js » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698