Mozilla 2/2008Q2 Goals: Difference between revisions
Jump to navigation
Jump to search
(→ActionMonkey: Some concrete goals for ActionMonkey) |
|||
| Line 19: | Line 19: | ||
== ActionMonkey == | == ActionMonkey == | ||
<ul> | |||
<li>Merge Tamarin Central's GC into Tamarin Tracing ({{bug|409021}}).</li> | |||
<li>Replace Tamarin Central with Tamarin Tracing in ActionMonkey ({{bug|425818}}).</li> | |||
<li>Merge SpiderMonkey's property tree optimization into Tamarin Tracing ({{bug|427151}}).</li> | |||
== XPCOMGC == | == XPCOMGC == | ||
* Browser running mostly-correctly, and gather performance/memory statistics | * Browser running mostly-correctly, and gather performance/memory statistics | ||
Revision as of 00:04, 5 April 2008
These are the Mozilla 2 team goals for Q2 2008:
THIS IS A VERY ROUGH DRAFT.
Memory
- In jemalloc, implement no-fail OOM by default and a separate can-fail allocator API: see Mozilla 2/Memory
- Implement the automatic-rewriting pass to get rid of null-checks for OOM. NOTE: this doesn't mean we will actually land the patch this quarter; that depends on identifying "large allocations" and exempting them from the normal rules
- jemalloc+GC API design complete, see GC_API
Automatic Rewriting/Analysis
- Finish dehydra and deploy on debug+leak tinderboxes, linux and mac
- Finish analysis passes needed for XPCOMGC
- See OOM goal above
- GCC summit presentation and continuing GCC community involvement
- Release Dehydra 1.0 and Pork
ActionMonkey
- Merge Tamarin Central's GC into Tamarin Tracing (bug 409021).
- Replace Tamarin Central with Tamarin Tracing in ActionMonkey (bug 425818).
- Merge SpiderMonkey's property tree optimization into Tamarin Tracing (bug 427151).
- Browser running mostly-correctly, and gather performance/memory statistics