638
edits
JavaScript:ActionMonkey: Difference between revisions
add stage 2 and 3
(→How to build: adding link to build on windows) |
(add stage 2 and 3) |
||
| Line 66: | Line 66: | ||
* {{bug|394297}} - Make MMgc thread-safe (as a compile-time option) | * {{bug|394297}} - Make MMgc thread-safe (as a compile-time option) | ||
* {{bug|392602}} - Implement a new heuristic for JS_MaybeGC | * {{bug|392602}} - Implement a new heuristic for JS_MaybeGC | ||
== Stage 2 == | |||
(speculative) | |||
Merge SpiderMonkey and Tamarin object models. The result will be an ActionMonkey that uses the SpiderMonkey compiler and interpreter, and Tamarin objects and memory management. | |||
This would include tasks like: | |||
* Build system: link Tamarin (as a static or dynamic library) into ActionMonkey (and the browser). | |||
* Merge SpiderMonkey's property tree optimization into Tamarin. | |||
* Merge SpiderMonkey's JS_THREADSAFE handling of property accesses (see [http://developer.mozilla.org/en/docs/SpiderMonkey_Internals:_Thread_Safety SpiderMonkey Internals: Thread Safety]) into Tamarin. | |||
* Merge SpiderMonkey string optimizations into Tamarin. | |||
* Compare Tamarin and SpiderMonkey E4X behavior. | |||
== Stage 3 == | |||
(speculative) | |||
Merge the Tamarin interpreter and JIT into ActionMonkey. The result will be an ActionMonkey that uses the SpiderMonkey compiler to generate Tamarin bytecode, and uses Tamarin to execute it. | |||