149310 2015-09-17 15:53:11 -0700 Optimize WebAssembly calls 2016-12-20 14:34:26 -0800 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 sukolsak webkit-unassigned fpizlo ggaren mark.lam saam sukolsak oldest_to_newest 1126910 0 sukolsak 2015-09-17 15:53:11 -0700 Currently, when a WebAssembly function calls another function (JS or WASM), it will type check the return value and coerce it into the expected type. Similarly, when a WebAssembly function is called by another function (JS or WASM), it will type check the arguments and coerce them into the expected types. We can avoid this type checking and type coercion if we know that the caller or the callee is a WebAssembly function, because WebAssembly is statically typed. We can probably take it further by avoiding boxing and unboxing of values completely when a WebAssembly function calls another WebAssembly function. 1126912 1 sukolsak 2015-09-17 15:56:55 -0700 See also: Geoff's comments https://bugs.webkit.org/show_bug.cgi?id=149033#c6