SpiderMonkey (software)

From Wikipedia, the free encyclopedia
  (Redirected from JägerMonkey)
Jump to: navigation, search
SpiderMonkey
Developer(s) Mozilla Foundation / Mozilla Corporation
Development status Active
Written in C/C++
Operating system Cross-platform
Platform IA-32, x86-64, ARM, MIPS, SPARC [1]
Type JavaScript engine
License MPL[2]
Website developer.mozilla.org/en/SpiderMonkey

SpiderMonkey is the code name for the first-ever JavaScript engine, written by Brendan Eich at Netscape Communications, later released as open source and now[when?] maintained by the Mozilla Foundation. SpiderMonkey currently[when?] provides JavaScript support for Mozilla Firefox and various embeddings such as the GNOME 3 desktop.

History[edit]

Eich "wrote JavaScript in ten days" in 1995,[3] having been "recruited to Netscape with the promise of 'doing Scheme' in the browser".[4] (The idea of using Scheme was abandoned when "engineering management [decided] that the language must ‘look like Java’".[4]) In the fall of 1996, Eich, needing to "pay off [the] substantial technical debt" left from the first year, "stayed home for two weeks to rewrite Mocha as the codebase that became known as SpiderMonkey".[3] The name SpiderMonkey was chosen as a reference to the movie Beavis and Butt-head Do America, in which the character Tom Anderson mentions that the title characters were "whacking off like a couple of spider monkeys."[5] In 2011, Eich transferred management of the SpiderMonkey code to Dave Mandelin.[3]

TraceMonkey[edit]

TraceMonkey was the first JIT compiler written for the JavaScript language. The compiler was first released as part of SpiderMonkey in Firefox 3.5, providing "performance improvements ranging between 20 and 40 times faster" than the baseline interpreter in Firefox 3.[6]

Instead of compiling whole functions, TraceMonkey was a tracing JIT, which operates by recording control flow and data types during interpreter execution. This data then informed the construction of Trace Trees, highly specialized paths of native code.

Improvements to JägerMonkey eventually made TraceMonkey obsolete, especially with the development of the SpiderMonkey type inference engine. TraceMonkey is absent from SpiderMonkey from Firefox 11 onward.[7]

JägerMonkey[edit]

JägerMonkey, internally named MethodJIT, was a whole-method JIT compiler designed to improve performance in cases where TraceMonkey could not generate stable native code.[8][9] It was first released in Firefox 4 and eventually entirely supplanted TraceMonkey. It has itself been replaced by IonMonkey.

JägerMonkey operated very differently from other compilers in its class: while typical compilers worked by constructing and optimizing a control flow graph representing the function, JägerMonkey instead operated by iterating linearly forward through SpiderMonkey bytecode, the internal function representation. Although this prohibits optimizations that require instruction reordering, JägerMonkey compiling has the advantage of being very fast, which is useful for JavaScript since recompiling due to changing variable types is frequent.

Mozilla implemented a number of critical optimizations in JägerMonkey, most importantly polymorphic inline caches and type inference.[10]

The difference between TraceMonkey and JägerMonkey JIT techniques and the need for both was explained in a hacks.mozilla.org article. A more in-depth explanation of the technical details was provided by Chris Leary, one of SpiderMonkey's developers, in a blog post. More technical information can be found in other developer's blogs: dvander, dmandelin.

Standards[edit]

SpiderMonkey implements ECMA-262 edition 5.1 (ECMAScript) and several added features. ECMA-357 (ECMAScript for XML (E4X)) was dropped in early 2013 .[11]

Even though SpiderMonkey is used in Firefox, it does not provide host environments such as Document Object Model (DOM).

Internals[edit]

SpiderMonkey is written in C/C++ and contains an interpreter, the IonMonkey JIT compiler, and a garbage collector.

IonMonkey[edit]

IonMonkey is the name of Mozilla’s current JavaScript JIT compiler, which aims to enable many new optimizations that were impossible with the prior JägerMonkey architecture.[12]

IonMonkey is a more traditional compiler: it translates SpiderMonkey bytecode into a control flow graph, using static single assignment form (SSA) for the intermediate representation. This architecture enables well-known optimizations from other programming languages to be used for JavaScript, including type specialization, function inlining, linear-scan register allocation, dead code elimination, and loop-invariant code motion.[13]

The compiler can emit fast native code translations of JavaScript functions on the ARM, x86, and x86-64 platforms. It is the default engine since Firefox 18.[14]

OdinMonkey[edit]

OdinMonkey is the name of Mozilla's new optimization module for asm.js, an easily compilable subset of JavaScript. OdinMonkey itself is not a JIT compiler, it uses the current JIT compiler. It's included with Firefox from release 22.

Use[edit]

SpiderMonkey is intended to be embedded in other applications that provide host environments for JavaScript. An incomplete list follows:

SpiderMonkey includes a JavaScript Shell for interactive JavaScript development and for command-line invocation of JavaScript program files.[18]

Several[quantify] large organizations use SpiderMonkey to manage their JavaScript for front-end applications.

See also[edit]

References[edit]

  1. ^ "1.8.8 - SpiderMonkey | MDN". Developer.mozilla.org. 2013-01-10. Retrieved 2013-03-21. 
  2. ^ Mozilla Licensing Policies, mozilla.org, retrieved 26 March 2013 
  3. ^ a b c Eich, Brendan (21 June 2011). "New JavaScript Engine Module Owner". BrendanEich.com. 
  4. ^ a b Eich, Brendan (3 April 2008). "Popularity". BrendanEich.com. 
  5. ^ Eich, Brendan (19 August 2011). "Mapping the Monkeysphere". 
  6. ^ Paul, Ryan (2008-08-22). "Firefox to get massive JavaScript performance boost". Ars Technica. Retrieved 2013-03-21. 
  7. ^ Nethercote, Nicholas (2011-11-01). "SpiderMonkey is on a diet | Nicholas Nethercote". Blog.mozilla.com. Retrieved 2013-03-21. 
  8. ^ "JaegerMonkey – Fast JavaScript, Always! » Mystery Bail Theater". Bailopan.net. 2010-02-26. Retrieved 2013-03-21. 
  9. ^ Paul, Ryan (2010-03-09). "Mozilla borrows from WebKit to build fast new JS engine". Ars Technica. Retrieved 2013-03-21. 
  10. ^ "JaegerMonkey - MozillaWiki". Wiki.mozilla.org. Retrieved 2013-03-21. 
  11. ^ "759422 – Remove use of e4x in account creation". Retrieved 5 February 2013. 
  12. ^ "Platform/Features/IonMonkey - MozillaWiki". Wiki.mozilla.org. 2013-02-11. Retrieved 2013-03-21. 
  13. ^ "IonMonkey: Mozilla’s new JavaScript JIT compiler". Infoq.com. Retrieved 2013-03-21. 
  14. ^ "Firefox Notes - Desktop". Mozilla.org. 2013-01-08. Retrieved 2013-03-21. 
  15. ^ Bolso, Erik Inge (8 March 2005). "2005 Text Mode Browser Roundup". Linux Journal. Retrieved 5 August 2010. 
  16. ^ wine-cvs mailing list, 16 September 2008: "jscript: Added regular expression compiler based on Mozilla regexp implementation"
  17. ^ "The Release Riak 0.8 and JavaScript Map/Reduce". Retrieved 2011-04-24. 
  18. ^ "Introduction to the JavaScript shell". MDN. Mozilla Developer Network. 2010-09-29. Retrieved 2010-12-14. The JavaScript shell is a command-line program included in the SpiderMonkey source distribution. [...] You can use it as an interactive shell [...] You can also pass in, on the command line, a JavaScript program file to run [...] 

External links[edit]