JavaScript:TraceMonkey

Revision as of 20:45, 15 July 2008 by Gal (talk | contribs) (New page: == TraceMonkey Tasks == Here are a few pending tasks. Most of them benefit Tamarin-Tracing and TraceMonkey. Tasks that only benefit TraceMonkey are marked with a star(*). * Setup perform...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

TraceMonkey Tasks

Here are a few pending tasks. Most of them benefit Tamarin-Tracing and TraceMonkey. Tasks that only benefit TraceMonkey are marked with a star(*).

  • Setup performance & compliance test framework for shell using a MacMini.(*)
    • Skill set: perl, shell scripts and such
    • Effort: couple days tops
  • Cleanup page allocation code in nanojit.
    • Skill set: C/C++, gdb, some understanding of Tamarin would be good
    • Effort: 1 week
  • Make more JSOPs traceable.(*)
    • Skill set: solid experience with SpiderMonkey
    • Effort: on-going
  • Implement soft-float math in TraceMonkey. The code already exists in Tamarin-Tracing and just needs to be ported over. Coordinate with upstream maintainer to extract soft-float code into a filter and get a patch for that into Tamarin-Tracing.
    • Skill set: C/C++, gdb, no fear of ARM assembly
    • Effort: 2 weeks
  • Add loop-spanning register allocation to nanojit and get patch into Tamarin-Tracing.
    • Skill set: C/C++, gdb, experience with compiler construction advisable
    • Effort: 2-4 weeks, depending on implementation strategy
  • Help Intel with type stability analysis on real-world JS code.
    • Skill set: understanding of JS, C/C++
    • Effort: 2 weeks
  • Port nanojit to PowerPC (lower priority).
    • Skill set: solid understanding of architecture issues, C/C++, lots of gdb
    • Effort: 4 weeks