News for hackers. Stuff that matters.

A comment on Firefox’s new streaming and tiering compiler. Parent comment

Re:Firefox’s new streaming and tiering compiler by luke_wagner on Wednesday January 17, 2018 @01:39PM (#16170496)
To wit, as described in their blog post: https://blogs.windows.com/msedgedev/2017/04/20/improved- Edge validates and compiles wasm code lazily. Thus, this simplistic benchmark isn't really measuring compile time on Edge. In contrast, Firefox, Chrome and Safari are doing some amount of AOT compilation before WebAssembly.instantiate() resolves.
[ Parent | on HN ]
Re:Firefox’s new streaming and tiering compiler by ehsankia on Wednesday January 17, 2018 @01:48PM (#16170571)
Here's a stupid question, but is the result of the Firefox and Chrome "instantiate" the exact same? Is the compilation doing the same job, or one could be performing more optimizations? Aka faster compilation but slower execution.
[ Parent | on HN ]
Re:Firefox’s new streaming and tiering compiler by computerphage on Wednesday January 17, 2018 @08:12PM (#16173767)
They're doing slightly different things, but not to nearly the extent of Edge which is doing something very different.
[ Parent | on HN ]