Asm.js

Design

asm.js enables significant performance improvements for web applications, but does not aim to improve the performance of hand-written JavaScript code, nor does it enable anything other than enhanced performance.

It is intended to have performance characteristics closer to that of native code than standard JavaScript by limiting language features to those amenable to ahead-of-time optimization and other performance improvements.^[4] By using a subset of JavaScript, asm.js is largely supported by all major web browsers,^[5] unlike alternative approaches such as Google Native Client.

Code generation

This section does not cite any sources. Please help improve this section by adding citations to reliable sources. Unsourced material may be challenged and removed. (March 2015) (Learn how and when to remove this template message)

asm.js is not typically written directly: instead, as an intermediate language, it is generated through the use of a compiler that takes source code in a language such as C++ and outputs asm.js.

For example, given the following C code:

int f(int i) {
  return i + 1;
}

Emscripten would output the following JS code:

function f(i) {
  i = i|0;
  return (i + 1)|0;
}

Note the addition of |0 and the lack of type specifiers. In JavaScript, bitwise operators convert their operands to 32-bit signed integers and give integer results. This means that a bitwise OR with zero converts a value to an integer (a very simple "conceptual" presentation of bitwise operators may not deal with type conversion at all, but every programming language defines operators for its own convenience, as Javascript does here). By doing this for each parameter, this ensures that if the function is called from outside code, the value will be converted to the correct type. This is also used on the return value, in this case to ensure that the result of adding 1 to i will be an integer (as otherwise it could become too large), and to mark the return type of the function. These conversions are required by asm.js, so that an optimising compiler can produce highly efficient native code ahead-of-time. In such an optimising compiler, no conversions are performed when asm.js code calls other asm.js code, as the required type specifiers mean it is guaranteed that values will already have the correct type. Furthermore, rather than performing a floating-point addition and converting to an integer, it can simply do a native integer operation. Together, this leads to significant performance benefits.

Here is another example to calculate the length of a string:

size_t strlen(char *ptr) {
  char *curr = ptr;
  while (*curr != 0) {
    curr++;
  }
  return (curr - ptr);
}

This would result in the following asm.js code:

function strlen(ptr) {
  ptr = ptr|0;
  var curr = 0;
  curr = ptr;
  while ((MEM8[curr>>0]|0) != 0) {
    curr = (curr + 1)|0;
  }
  return (curr - ptr)|0;
}

In the generated code, the variable MEM8 is actually a byte-by-byte "view" of a typed buffer, which serves as the "heap" of the asm.js code.

Performance

Since asm.js runs in a browser, the performance heavily depends on both the browser and hardware. Preliminary benchmarks of C programs compiled to asm.js are usually within a factor of 2 slowdown over native compilation with Clang.^[6]

Much of this performance gain over normal JavaScript is due to 100% type consistency and virtually no garbage collection (memory is manually managed in a large typed array). This simpler model with no dynamic behavior, no memory allocation or deallocation, just a narrow set of well-defined integer and floating point operations enables much greater performance and potential for optimization.^{[citation needed]}

Mozilla's benchmark from December 2013 showed significant improvements: "Firefox with float32 optimizations can run all those benchmarks at around 1.5× slower than native, or better."^[7] Mozilla points out that the performance of natively compiled code is not a single measure but rather a range, with different native compilers (in this case Clang and GCC) delivering code of differing performance. "In fact, on some benchmarks, like Box2D, FASTA and copy, asm.js is as close or closer to Clang than Clang is to GCC. In one case, asm.js even beats Clang by a slight amount on Box2D."^[7]

Implementations

The Emscripten project provides tools that can be used to compile C and C++ codebases (or any other languages that can be converted to LLVM IR) into asm.js.^[2]

All browsers with support for ECMAScript 6 should be able to run asm.js code, as it is a subset of that specification. However, since features were added in that edition to enable full asm.js support (Math.fround()), older browsers lacking those features may encounter problems.

Some browser implementations are especially optimised for asm.js:

• Mozilla Firefox was the first web browser to implement asm.js-specific optimizations, starting with Firefox 22.^[3]OdinMonkey, Mozilla's asm.js ahead-of-time compiler used in Firefox, is a component of IonMonkey, the JIT compiler of SpiderMonkey.
• Microsoft is implementing support for asm.js in Chakra, the JavaScript engine used by Microsoft Edge, performing validation to produce highly optimised JIT code.^[8]
• The optimizations of Google Chrome's V8 JavaScript engine in Chrome 28 made asm.js benchmarks more than twice as fast as prior versions of Chrome,^[9] although Chrome's V8 does not use ahead-of-time compilation.

Adoption

This section relies too much on references to primary sources. Please improve this section by adding secondary or tertiary sources. (March 2015) (Learn how and when to remove this template message)

Almost all of the current applications based on asm.js are C/C++ applications compiled to asm.js using Emscripten or Mandreel. With that in mind, the kind of applications that are going to target asm.js in the near future are those that will benefit from the portability of running in a browser but which have a level of complexity for which a direct port to JavaScript would be infeasible.

So far, a number of programming languages, application frameworks, programs, libraries, games, game engines and other software have already been ported.^[10] Some of them are given below.

Programming languages

• C/C++: Clang and LLVM
• Rust: targets Emscripten
• Lua VM: Lua virtual machine^[11]
• Perl: port of (micro)perl-5.16.3^[12]
• Python – port of CPython^[13]
• Ruby – port of Ruby^[14]

Application frameworks

• pepper.js: Ports of miscellaneous PNaCl apps (earth, voronoi, bullet, etc.)^[15]
• Qt: ports of various Qt demos, plus KDE apps, such as Kate^[16]

Programs and libraries

• OpenGL, SDL, and SDL2^[17]
• Vim (Vi IMproved)^[18]
• FreeType: TrueType font rendering in JavaScript, using FreeType^[19]
• SQLite^[20]
• GNU Privacy Guard^[21]
• ctags^[22]
• gnuplot^[23]
• Graphviz^[24]
• zlib^[25]

Game engines

• Unreal Engine 3: was ported in 4 days^[26][27]
• Unreal Engine 4
• Unity^[28]
• ScummVM, which supports numerous classic adventure games^[29]
• Godot^[30]

Games

• Doom: the open source Freedoom game assets running on PrBoom, which is based on the open source Doom code^[31]
• SuperTux^[32]
• Dune II via OpenDune^[33]
• BananaBread based on Cube 2^[34]
• Every game in the Humble Mozilla Bundle^[35] (Super Hexagon, AaAaAA! for the Awesome, Osmos, Zen Bound 2, Dustforce DX, Voxatron, FTL: Advanced Edition and Democracy 3)

Emulators

• EM-DOSBox: an Emscripten port of DOSBox^[36]
• Start9.io: a web emulation platform targeting multiple gaming architectures
• JSMESS: a port of the MESS emulator for many game consoles and computer systems^[37]

Mathematics

• HTML5 Fractal Playground^[38] – draws iterating-function generated fractals, such as the Mandelbrot set.

Deprecation

asm.js is mostly rendered obsolete with the introduction of WebAssembly (wasm), which has a bytecode format that is faster to parse.^[39] Efforts to extend JavaScript with more low-level features like SIMD.js has also been suspended since 2017.^[40]

asm.js remains useful primarily as a "fallback" for wasm, through a program written by the WebAssembly organization that converts wasm to asm.js. There is no dedicated converter from asm.js to wasm, but TypeScript-to-wasm compilers can be partially used.^[41] The reference WebAssembly emitter binaryen used to contain an asm2wasm module, but it was removed after Emscripten stopped using it.^[42]

See also

• CrossBridge
• Emscripten
• Google Native Client (NaCl)
• RPython
• WebAssembly – a bytecode for browsers, intended to be faster to parse than asm.js

References

External links

• Official website