maybe asm.js?

[E. M. Marston]

Hi all,

I'm new here, so please forgive me if I'm not posting this in the right place, or if the discussion has already occurred somewhere not amenable to my googlings.

Is there any thought to folding in awareness of asm.js-optimized code into v8? As a front-end dev with a penchant for good old C, I'm super-excited about asm.js, but 'einmal ist keinmal'; it won't count as the new hotness until it has more than one browser behind it.

Enabling a powerful new technology like asm.js is definitely within the ambit of Chrome and V8. There will be a missed opportunity for the whole web unless there is cross-engine support for asm.js.

The first sprint wouldn't necessarily need to do anything other than recognize the asm.js directive; implementing actual optimisation, so that asm.js code runs faster than other ECMAScript code, could be done iteratively and progressively over many months. 

I might start working on it myself if there's no interest from someone with less ramp-up time (I'm a newcomer to the V8 project.)

~Beth
(and thanks for v8 <3)

[Daniel Clifford]

Hi,

There is no "support" that needs to be added to make asm.js-style code run in Chrome. It already does.

I don't see any missed opportunity for the whole web. We're always optimizing V8 to run JavaScript code faster. The asm.js use-case is just one of many. We prioritize our optimization work by overall impact. Optimizations that will benefit the large body of typical JavaScript code that is already out there--and not just asm.js-style code--tend to top our to-do list, and I currently don't see a reason to change that.

Danno

--
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups "v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.