Tamarin:Tracing: Difference between revisions
Jump to navigation
Jump to search
(Adding links to Bluish Coder blog.) |
No edit summary |
||
| Line 11: | Line 11: | ||
* [http://www.bluishcoder.co.nz/2008/02/quick-introduction-to-tamarin-tracing.html A Quick Introduction to Tamarin Tracing] | * [http://www.bluishcoder.co.nz/2008/02/quick-introduction-to-tamarin-tracing.html A Quick Introduction to Tamarin Tracing] | ||
* [http://www.bluishcoder.co.nz/2008/02/implementing-native-methods-in-tamarin.html Implementing Native Methods in Tamarin Tracing] | * [http://www.bluishcoder.co.nz/2008/02/implementing-native-methods-in-tamarin.html Implementing Native Methods in Tamarin Tracing] | ||
* [http://blog.mozilla.com/dmandelin/2008/05/16/tamarin-tracing-internals-part-i/ Tamarin Tracing internals part I] | |||
== Background Information == | == Background Information == | ||
Revision as of 20:24, 23 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
- Tamarin Tracing internals part I
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