5 ms·

Not sure where you see "spec" mentioned in there? As you say, Google included asm.js code in Octane 2, and you can see progress on asm.js benchmarks as Google

by azakai 13y ago

Not sure where you see "spec" mentioned in there? As you say, Google included asm.js code in Octane 2, and you can see progress on asm.js benchmarks as Google optimizes in ways that help that style of code on arewefastyet, http://arewefastyet.com/#machine=11&view=breakdown&suite=asmjs-ubench http://arewefastyet.com/#machine=11&view=breakdown&suite=asm... This is also not something new, Google has optimized for asm.js code since the IO keynote much earlier this year where Google reported a 2.4x speedup on an aggregate asm.js benchmark, http://culturemass.com/2013/05/17/google-io-2013-keynote-part-ii/ http://culturemass.com/2013/05/17/google-io-2013-keynote-par... There are many ways to optimize for different types of code. Firefox uses the asm.js type system for asm.js, and does AOT compilation, while Chrome chose a different approach. The two approaches have different benefits. But both browsers certainly optimize for asm.js, they both announced doing so and the numbers are proof that they are succeeding. edit: add link to Octane 2.0 and the asm.js benchmark added there, http://blog.chromium.org/2013/11/announcing-octane-20.html http://blog.chromium.org/2013/11/announcing-octane-20.html

rictic 13y ago
Even before asm.js there was emscripten (the primary generator of asm.js and inspiration for much of the spec), which has been used for a number of high profile demos and likely got optimization attention for years before asm.js.
- cpeterso 13y ago
  I'm sure azakai is familiar with emscripten. ;)
  - girvo 13y ago
    This doesn't happen anywhere except on HN. I check parents profile before I ever reply for this reason ;)
deleted 13y ago
[deleted]
deleted 13y ago
[deleted]
cromwellian 13y ago
When we released gwtquake it ran poorly on FF and the FF team seems to have spent some time optimizing for it. Imagine a press release boasting how FF optimizes for GWT. This press release is a little heavy on spin trying to market asmjs. While it does appear V8 is speeding up asmjs style code, until we know specifically about what they've done in chrome 31/32, this seems mostly like speculation. What if in fact asmjs was causing a degenerate case in their JIT and what they actually did amounted to fixing some bugs?
- pcwalton 13y ago
  > What if in fact asmjs was causing a degenerate case in their JIT and what they actually did amounted to fixing some bugs? I don't see how that's any different from optimizing for asm.js. Optimization is often about fixing bugs.

by azakai 13y ago

rictic 13y ago

Even before asm.js there was emscripten (the primary generator of asm.js and inspiration for much of the spec), which has been used for a number of high profile demos and likely got optimization attention for years before asm.js.

cpeterso 13y ago
I'm sure azakai is familiar with emscripten. ;)
- girvo 13y ago
  This doesn't happen anywhere except on HN. I check parents profile before I ever reply for this reason ;)

deleted 13y ago

[deleted]

deleted 13y ago

[deleted]

cromwellian 13y ago

When we released gwtquake it ran poorly on FF and the FF team seems to have spent some time optimizing for it. Imagine a press release boasting how FF optimizes for GWT. This press release is a little heavy on spin trying to market asmjs. While it does appear V8 is speeding up asmjs style code, until we know specifically about what they've done in chrome 31/32, this seems mostly like speculation. What if in fact asmjs was causing a degenerate case in their JIT and what they actually did amounted to fixing some bugs?

pcwalton 13y ago
> What if in fact asmjs was causing a degenerate case in their JIT and what they actually did amounted to fixing some bugs? I don't see how that's any different from optimizing for asm.js. Optimization is often about fixing bugs.