Tamarin:Tracing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
* [http://blog.mozilla.com/dmandelin/2008/05/21/tamarin-tracing-interals-part-ii-forth/ Tamarin Tracing Interals, Part II: Forth] | * [http://blog.mozilla.com/dmandelin/2008/05/21/tamarin-tracing-interals-part-ii-forth/ Tamarin Tracing Interals, Part II: Forth] | ||
* [http://blog.mozilla.com/dmandelin/2008/05/23/tamarin-tracing-internals-iii-lir/ Tamarin Tracing Internals III: LIR] | * [http://blog.mozilla.com/dmandelin/2008/05/23/tamarin-tracing-internals-iii-lir/ Tamarin Tracing Internals III: LIR] | ||
* [http://blog.mozilla.com/dmandelin/2008/05/28/tamarin-tracing-internals-iv-trace-optimization/ Tamarin Tracing Internals IV: Trace Optimization] | |||
* [http://blog.mozilla.com/dmandelin/2008/05/28/tamarin-tracing-internals-v-running-compiled-traces/ Tamarin Tracing Internals V: Running Compiled Traces] | |||
== Background Information == | == Background Information == | ||
Revision as of 19:23, 30 May 2008
Tamarin-tracing is an experimental branch of the Tamarin virtual machine. This branch modifies tamarin to use a trace-based optimizer rather than a conventional just-in-time compiler. Trace optimization is a technique which holds promise for optimizing untyped javascript code, and doing so with a small memory footprint.
The new branch can be found in http://hg.mozilla.org/tamarin-tracing/.
External References
- A Quick Introduction to Tamarin Tracing
- Implementing Native Methods in Tamarin Tracing
- Extending Tamarin Tracing with Forth
- Tamarin Tracing internals part I
- Tamarin Tracing Interals, Part II: Forth
- Tamarin Tracing Internals III: LIR
- Tamarin Tracing Internals IV: Trace Optimization
- Tamarin Tracing Internals V: Running Compiled Traces
Background Information
- Incremental Dynamic Code Generation with Trace Trees
- Making the Compilation Pipeline Explicit: Dynamic Compilation Using Trace Tree Serialization
- HotpathVM: An Effective JIT Compiler for Resource-constrained Devices
- Efficient Just-In-Time Execution of Dynamically Typed Languages Via Code Specialization Using Precise Runtime Type Inference