638
edits
JavaScript:ActionMonkey: Difference between revisions
Jump to navigation
Jump to search
→Stage 5: +pessimism
(→How to build: Note that autoconf-2.13 is required.) |
(→Stage 5: +pessimism) |
||
| Line 137: | Line 137: | ||
(speculative) | (speculative) | ||
Merge the | Merge the <code>tamarin-tracing</code> interpreter and JIT into ActionMonkey. The result will be an ActionMonkey that uses the SpiderMonkey compiler to generate Tamarin bytecode, and uses Tamarin to execute it. | ||
Known risks: | |||
* We'll likely be the first to use tamarin-tracing in a product. :) | |||
* tamarin-tracing is not reentrant. The official plan is to "come up with some disgusting hack". We won't know how the performance is until we try it. | |||
* tamarin-tracing doesn't have <code>eval</code>. (We'll supply the compiler, of course. But <code>eval</code> also needs: a way to load and run bytecode from memory without going to disk; and support for a dynamic global object.) | |||