Mozilla 2/2008Q2 Goals: Difference between revisions

→‎ActionMonkey: Drop JS_THREADSAFE
(move the XPCOMGC rewriting pass)
(→‎ActionMonkey: Drop JS_THREADSAFE)
Line 26: Line 26:
* 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.
* 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 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}}).
* Merge SpiderMonkey's string optimizations into Tamarin Tracing ({{bug|427154}}).


Confirmed users
496

edits