638
edits
JavaScript:ActionMonkey: Difference between revisions
Jump to navigation
Jump to search
add XPCOMGC work we agreed on in Toronto; put off Tamarin integration for a few months
(add XPCOMGC work we agreed on in Toronto; put off Tamarin integration for a few months) |
|||
| Line 68: | Line 68: | ||
== Stage 2 == | == Stage 2 == | ||
Incremental GC for Mozilla. | |||
* Make MMgc thread-safe when incremental GC is enabled. | |||
* Enable incremental GC in Mozilla. This implies adding write barriers to the appropriate places in <tt>js/src</tt>, to make it work with incremental GC. | |||
== Stage 3 == | |||
Land XPCOMGC in actionmonkey branch. This is going to be ''interesting'', given the nature of the XPCOMGC patch stack. We need to figure out what this actually means. | |||
Then, | |||
* Debug. | |||
* Tune the resulting platform, producing meaningful performance numbers. | |||
== Stage 4 == | |||
(speculative) | (speculative) | ||
| Line 81: | Line 97: | ||
* Compare Tamarin and SpiderMonkey E4X behavior. | * Compare Tamarin and SpiderMonkey E4X behavior. | ||
== Stage | == Stage 5 == | ||
(speculative) | (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. | 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. | ||