My understanding is that asm.js is all or nothing. It is designed as a target for languages that manage their own memory (that is generally not garbage collected, but you could implement garbage collection in such a system). Firefox looks at the JavaScript and decides if it is asm.js, then switches to another JavaScript interpreter that is optimized for asm.js. If this interpreter detects anything outside of the asm.js subset, it kicks all execution back to the standard interpreter. This means you can't pick part of a gwt compile to target asm.js; it would be all on none.
Ed On Thursday, May 23, 2013 12:52:00 AM UTC-7, RyanZA wrote: > > Have a quick read through this article if you don't know what asm.js is: > > http://arstechnica.com/information-technology/2013/05/native-level-performance-on-the-web-a-brief-examination-of-asm-js/ > > With firefox already supporting it, GWT should have the firefox compile > target target asm.js for, at least, things like ArrayList. > I didn't see anything about it in the recent I/O talk - has anybody looked > at how difficult it would be to support in the GWT compiler ? > > Ryan > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
