Hi Luke, Thank you for your reply. I agree that #2 will be unnecessary if the jit compilation process can be controlled by developers. I've read bug 854627 and found it was not implemented yet. I'm glad to work on this feature if there is no one working on it.
On Tue, Apr 16, 2013 at 11:54 PM, Luke Wagner <[email protected]> wrote: > Hi Wei Wu, > > I'm glad to hear that you are interested. I'd like to comment on #2: > > > 2. Cache compiled asm.js codes and IR to avoid runtime overhead. > > Mozilla proposed asm.js as a low-level, efficient target language for > > compilers[4]. Emscripten is the main producer of asm.js codes > > currently. The asm.js codes translated by Emscripten are not changed > frequently, > > compare with typical JavaScript codes written by programmers, and it > > will never bailout. It may be feasible to store both IR and binary for > > load time speedup and further optimizations. > > We have plans to give the developer explicit control over parallel > compilation and jit-code caching (via IndexedDB) with the addition of a new > FunctionFuture primitive [1], so this may not be necessary. > > Cheers, > Luke > > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=854627 > -- 吴伟(Wei Wu) _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
