638
edits
Mozilla 2/2008Q2 Goals: Difference between revisions
Jump to navigation
Jump to search
add my goals... *shudder*
(→Memory) |
(add my goals... *shudder*) |
||
| Line 20: | Line 20: | ||
== ActionMonkey == | == ActionMonkey == | ||
* Finish ActionMonkey Stage 2 by the end of April {{bug|411563}}. (The big wild card is the "no speed regression" requirement.) | |||
* Get the [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla2 ActionMonkey tinderboxen] green, and the browser functional in actionmonkey branch, and keep them that way. | |||
* Merge Tamarin Central's GC into Tamarin Tracing ({{bug|409021}}). | |||
* Replace Tamarin Central with Tamarin Tracing in ActionMonkey ({{bug|425818}}). | |||
* Understand both SpiderMonkey and Tamarin-tracing object representation, including consequences for speed, memory usage, security, and host objects (embedding-defined object types—how they are defined, how they interact with the VM). This is a tall order but seems like a prerequisite to the rest. | |||
* Merge SpiderMonkey's property tree optimization into Tamarin Tracing ({{bug|427151}}). | |||
* 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 ({{bug|427158}}). | |||
* Merge SpiderMonkey's string optimizations into Tamarin Tracing ({{bug|427154}}). | |||
* Finish [[GC API]] design. | |||
== XPCOMGC == | == XPCOMGC == | ||
* Browser running mostly-correctly, and gather performance/memory statistics | * Browser running mostly-correctly, and gather performance/memory statistics | ||