3 ms·
I think there's probably a subtle distinction that's hard to show. I'd imagine the line is drawn at interpreting the "use asm"; which signals the asm.js o
by pfraze 13y ago
I think there's probably a subtle distinction that's hard to show. I'd imagine the line is drawn at interpreting the
"use asm";
which signals the asm.js optimizations should be used. Instead, I'd bet the Chrome team are just watching for JS which matches the asm.js spec and optimizing for those cases, like they do for other code paths & structures. That would mean they are optimizing for it, but not supporting it directly.
- mraleph 13y ago> Instead, I'd bet the Chrome team are just watching for JS which matches the asm.js spec No. All optimizations that V8 are doing are following from the JavaScript specification itself, not from asm.js specification. V8 does not use asm.js specification in any way (including type rules that asm.js prescribes). If you take asm.js code and slightly change typing so that it will no longer pass asm.js type check but still be reasonable V8 will continue to optimize what it can.