Javascript:SpiderMonkey:OdinMonkey: Difference between revisions

m
Line 23: Line 23:
* Start general JS parsing before the entire JS script has completed downloading so that asm.js compilation can overlap
* Start general JS parsing before the entire JS script has completed downloading so that asm.js compilation can overlap
* Standardize and implement value objects ({{bug|749786}}) then add int64/uint64 to asm.js
* Standardize and implement value objects ({{bug|749786}}) then add int64/uint64 to asm.js
* asm.js parser : {{bug|854061}}
* asm.js parser: {{bug|854061}}
* Support GC allocated Java-like objects to allow asm.js generation from JVM/CLR bytecode.  Use [http://wiki.ecmascript.org/doku.php?id=harmony:typed_objects Typed Objects] to describe class structure.  Use real vtables.
* Support GC allocated Java-like objects to allow asm.js generation from JVM/CLR bytecode.  Use [http://wiki.ecmascript.org/doku.php?id=harmony:typed_objects Typed Objects] to describe class structure.  Use real vtables.
* fall back to baseline jit for very large functions (maybe not necessary with Emscripten [http://mozakai.blogspot.com/2013/08/outlining-workaround-for-jits-and-big.html outlining]): {{bug|875174}}
* fall back to baseline jit for very large functions (maybe not necessary with Emscripten [http://mozakai.blogspot.com/2013/08/outlining-workaround-for-jits-and-big.html outlining]): {{bug|875174}}
* FunctionFuture : {{bug|854627}}
* FunctionPromise: {{bug|854627}} (was FunctionFuture)


== Potential backend optimizations ==
== Potential backend optimizations ==
Confirmed users
247

edits