Playing with TraceMonkey
- open a new tab;
- type “about:config” and hit enter;
- read the warning and heed its wisdom;
- enter “jit” in the filter field;
If you experience instability, please file a bug and reference any crash report ID that might be relevant. As of 2009, of the stable builds only the 32-bit versions of Firefox have TraceMonkey available (use nightly builds for 64-bit support).
Hacking on TraceMonkey
The TM tree is located at http://hg.mozilla.org/tracemonkey.
We are currently still in rapid‐development mode. Our commit policy is as follows: if you are confident you know what you are doing, push now and prepare to answer questions later if you break the tree. If you have commit access to hg.mozilla.org, feel free to commit any patch you feel is sensible. Even white‐space clean‐up, additional comments or general code clean‐up/naming‐consistency changes are welcome.
Run trace-test.js and all benchmarks in t/* before you commit. Commits that break any of these tests are allowed if sensible, but please let everyone know why you break what and what has to happen to fix it.
The main channel to discuss TM is #jsapi on irc.mozilla.org.
- fuzzer bugs fixed
- slow script dialog
- perf matches a2
- test suites passing
- nanojit x86 (this works, but it must remain so)
- OOM nanojit/tracer testing
- disable tracer in the presence of debugger
- tracing recursion
- trace over DOM fast stubs (not into)
- event handler tracing
- ARM nanojit
- SSE opts
- PPC nanojit
- built‐in reg usage
- Nanojit Verifier